From mark at tinka.africa Tue Jan 7 04:37:31 2025 From: mark at tinka.africa (Mark Tinka) Date: Tue, 7 Jan 2025 06:37:31 +0200 Subject: [rpd] APRICOT 2025: Call for Papers - Reminder! In-Reply-To: <00aee8fa-ac19-4278-a92b-58444b8dc1af@tinka.africa> References: <00aee8fa-ac19-4278-a92b-58444b8dc1af@tinka.africa> Message-ID: <02674436-88ae-4eab-b9d4-e89a39b0cae6@tinka.africa> Greetings all, and a very Happy New Year! This is a gentle reminder to submit your presentation proposals for the upcoming APRICOT meeting in Kuala Lumpur as detailed below. We look forward to hearing from you. Mark. On 10/27/24 09:48, Mark Tinka wrote: > Hello all. > > The APRICOT 2025 Programme Committee is now seeking contributions for > Presentations and Tutorials for the APRICOT 2025 Conference, which > will be held in Petaling Jaya, Malaysia, 19th - 27th, February 2025. > > Details about the Call for Papers, and how you can submit a proposal > for a conference, peering and tutorial talk, and the submission > deadlines, can be found at the link below: > > https://2025.apricot.net/programme/callforpresentations > > We look forward to receiving your papers, and seeing you in Malaysia. > > Many thanks! > > Mark Tinka, Achie Atienza & Mark Duffell > APRICOT 2025 Programme Committee Chairs -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Mon Apr 7 12:45:07 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Mon, 7 Apr 2025 12:45:07 +0000 Subject: [rpd] Register for the "Stories of Resilience: Celebrating African Women Shaping Digital Transformation" Webinar on 17th April 2025. Message-ID: (Apologies for cross-posting) Dear Colleagues, You are invited to register for the "Stories of Resilience: Celebrating African Women Shaping Digital Transformation" Webinar. As we celebrate this year?s International Girls in ICT Day themed, ?Girls in ICT for Inclusive Digital Transformation,? we are reminded that Africa's digital future must be built by all and that includes the voices, innovations, and leadership of women. * Date: 17th April 2025 * Time: 10:00 -11:30 UTC * Duration: 1:30 Hrs * Registration link Across Africa, the digital revolution is reshaping economies, industries, and societies. Yet, despite the rapid growth of ICT, women remain significantly underrepresented in the sector. Structural barriers, societal expectations, and workplace biases continue to limit the participation of women in the very field that is driving the continent?s future. Despite the odds, there are trailblazing women across Africa who have defied these odds, risen to the challenge, shattered glass ceilings, and proved that the future of ICT must be inclusive. Through candid conversations, the webinar will highlight the challenges, triumphs, and impact of their work in a ?male-dominated? field. The panelists will offer insights, mentorship, and nuggets of wisdom to young women aspiring to break into and thrive in ICT, demonstrating that inclusion is not just necessary but essential for Africa?s digital future. This webinar is not just about storytelling, it is about building a movement that fosters diversity and equity in ICT, inspiring the next generation of African women to become leaders, innovators, and change makers in the digital space. Key Takeaways * Gain insights as to why diversity in ICT is crucial for Africa?s growth and how women can take the lead in shaping an inclusive digital transformation. * Learn from the real-life experiences of trailblazing African women in tech, as they share their challenges, achievements, and impact. * Be inspired and motivated to pursue a career in technology, with actionable lessons on breaking barriers and stepping into leadership roles in ICT. ________________________________ Secure your spot and register here. Be sure to save the date and spread the word as your participation is key to making these sessions a success! ________________________________ Explore the full schedule and learn more about each webinar both previous and upcoming on our Webinar Series Page. We look forward to having you join us for these insightful sessions! ________________________________ Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Mon Apr 14 13:08:06 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Mon, 14 Apr 2025 17:08:06 +0400 Subject: [rpd] ICP-2 Review: Share your feedback Message-ID: Dear Colleagues, The NRO NC has published a draft version of a document that aims to update ICP-2: Criteria for Establishment of New Regional Internet Registries. This updated document is titled ?Governance Document for the Recognition, Maintenance, and Derecognition of Regional Internet Registries? (RIR Governance Document) and can be viewed here https://www.nro.net/icp-2-rir-governance-document You are invited to provide your feedback and comments on the document from 14 April to 27 May 2025. Please keep the following in mind while preparing your comments: Please share feedback that is specific to this draft We are particularly interested in hearing your views on the new requirements in the draft Whether the draft provides sufficient clarity regarding the ongoing obligations of an RIR and the remediation steps if the obligations are not met This document does not address the implementation of the RIR criteria; comments on implementation will be considered out of scope Constructive comments are highly appreciated How to participate Share your feedback via the ICP-2 Review mailing list (requires subscription) at: https://lists.afrinic.net/mailman/listinfo/icp2-review or during an AFRINIC webinar. The details of the webinar will be provided shortly. Read more on ICP-2 Review at: https://www.afrinic.net/icp-2-review More information on the ICP-2 Review sessions are also published on the NRO website at: https://www.nro.net/policy/internet-coordination-policy-2/community-engagement/ We look forward to receiving your feedback in the ICP-2 Review mailing list. AFRINIC Communication -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Tue Apr 15 07:16:02 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Tue, 15 Apr 2025 07:16:02 +0000 Subject: [rpd] Reminder: Register for the "Stories of Resilience: Celebrating African Women Shaping Digital Transformation" Webinar on 17th April 2025. Message-ID: (Apologies for cross-posting) Dear Colleagues, Registration for the "Stories of Resilience: Celebrating African Women Shaping Digital Transformation" Webinar is ongoing. As we celebrate this year?s International Girls in ICT Day themed, ?Girls in ICT for Inclusive Digital Transformation,? we are reminded that Africa's digital future must be built by all and that includes the voices, innovations, and leadership of women. * Date: 17th April 2025 * Time: 10:00 -11:30 UTC * Duration: 1:30 Hrs * Registration link The session will be moderated by Ms. Sarah Kiden, Research Fellow at the University of Southampton. With her in the panel will be: * Mrs. Eyitayo Iyortim- Board Chairperson AfTLD * Mrs. Anne Rachel Inne - Digital for Development Consultant, Africa Ultimate Expertise * Mrs. Fiona Asonga - Chief Executive Officer, Tespok * Mrs. Wafa Dahmani - Stakeholder Development Liaison, AFRINIC * Ms. Manhal Mohammed- Senior Systems Engineer, AFRINIC * Mrs. Meriem Slimani - Development Coordinator, ATU Across Africa, the digital revolution is reshaping economies, industries, and societies. Yet, despite the rapid growth of ICT, women remain significantly underrepresented in the sector. Structural barriers, societal expectations, and workplace biases continue to limit the participation of women in the very field that is driving the continent?s future. Despite the odds, there are trailblazing women across Africa who have defied these odds, risen to the challenge, shattered glass ceilings, and proved that the future of ICT must be inclusive. Through candid conversations, the webinar will highlight the challenges, triumphs, and impact of their work in a ?male-dominated? field. The panelists will offer insights, mentorship, and nuggets of wisdom to young women aspiring to break into and thrive in ICT, demonstrating that inclusion is not just necessary but essential for Africa?s digital future. This webinar is not just about storytelling, it is about building a movement that fosters diversity and equity in ICT, inspiring the next generation of African women to become leaders, innovators, and change makers in the digital space. Key Takeaways * Gain insights as to why diversity in ICT is crucial for Africa?s growth and how women can take the lead in shaping an inclusive digital transformation. * Learn from the real-life experiences of trailblazing African women in tech, as they share their challenges, achievements, and impact. * Be inspired and motivated to pursue a career in technology, with actionable lessons on breaking barriers and stepping into leadership roles in ICT. ________________________________ Secure your spot and register here. Be sure to save the date and spread the word as your participation is key to making these sessions a success! ________________________________ Explore the full schedule and learn more about each webinar both previous and upcoming on our Webinar Series Page. We look forward to having you join us for these insightful sessions! ________________________________ Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Thu Apr 17 09:35:35 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Thu, 17 Apr 2025 09:35:35 +0000 Subject: [rpd] AFRINIC Webinar Series Streaming Shortly! Message-ID: (Apologies for Cross-posting) Dear Colleagues, The webinar on "Stories of Resilience: Celebrating African Women Shaping Digital Transformation" is about to start. If you are yet to register for this webinar, please do so here. If you are unable to join us on Zoom, we will be streaming the webinar live on our Youtube Page here. We look forward to your participation in this exciting webinar series and hope to see you there. Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Wed Apr 23 08:51:58 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Wed, 23 Apr 2025 08:51:58 +0000 Subject: [rpd] Register for the "ICP-2 Review" Webinar on 8th May 2025 Message-ID: (Apologies for cross-posting) Dear Colleagues, You are invited to register for the webinar on "ICP-2 Review" Webinar. * Date: Thursday 8 May 2025 * Time: 13:00 -14:00 UTC * Duration: 1:00 Hr * Moderator: Herv? Cl?ment * Panellists: Andrei Robachevsky and Maemura Akinori * Registration link The Internet landscape has changed significantly over the last two decades. The Number Resource Organization Executive Council (NRO EC), in conjunction with the Address Supporting Organization Address Council (ASO AC), decided it was time to review and update the Internet Coordination Policy (ICP-2) to meet current needs. In October 2023, the Number Resource Organization Executive Council (NRO EC) asked the NRO Number Council (NRO NC), that fulfils the role of the Address Supporting Organization Address Council (ASO AC), to establish and manage a process to update the ICP-2. Modification of ICP-2 requires an open and transparent process to allow participation from across the global RIR and ICANN communities. In this webinar, Number Resource Organization Number Council (NRO NC) members, Herv? Cl?ment, Andrei Robachevsky and Maemura Akinori will showcase the progress achieved so far in the ICP-2 Review. The session will also provide an introduction to the draft version of a document that aims to update ICP-2: Criteria for Establishment of New Regional Internet Registries. This updated document is titled "Governance Document for the Recognition, Maintenance, and Derecognition of Regional Internet Registries". This document is currently open for comments from 14 April to 27 May 2025. We invite community input on this draft document and encourage everyone interested in this topic to attend this session. We look forward to having your inputs in this webinar. Key Takeaways * Learn more on the progress achieved so far in the ICP-2 Review process * Gain insights into the draft version of the document that aims to update ICP-2: ?Governance Document for the Recognition, Maintenance, and Derecognition of Regional Internet Registries" * Get useful feedback from the community on the draft document Secure your spot and register here. Be sure to save the date and spread the word as your participation is key to making these sessions a success! ________________________________ Explore the full schedule and learn more about AFRINIC webinars on our Webinar Series Page. We look forward to having you join us for these insightful sessions! ________________________________ Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Mon May 5 06:46:22 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Mon, 5 May 2025 06:46:22 +0000 Subject: [rpd] Reminder: Register for the "ICP-2 Review" Webinar on 8th May 2025. Message-ID: (Apologies for cross-posting) Dear Colleagues, Registration for the "ICP-2 Review" Webinar is ongoing. * Date: Thursday 8 May 2025 * Time: 13:00 -14:00 UTC * Duration: 1:00 Hr * Moderator: Herv? Cl?ment * Registration link The session will be moderated by Mr. Herv? Cl?ment, Member, Number Resource Organization Number Council (NRO NC). With him in the panel will be: * Andrei Robachevsky- Member, Number Resource Organization Number Council (NRO NC) * Maemura Akinori - Member, Number Resource Organization Number Council (NRO NC) The Internet landscape has changed significantly over the last two decades. The Number Resource Organization Executive Council (NRO EC), in conjunction with the Address Supporting Organization Address Council (ASO AC), decided it was time to review and update the Internet Coordination Policy (ICP-2) to meet current needs. In October 2023, the Number Resource Organization Executive Council (NRO EC) asked the NRO Number Council (NRO NC), that fulfils the role of the Address Supporting Organization Address Council (ASO AC), to establish and manage a process to update the ICP-2. Modification of ICP-2 requires an open and transparent process to allow participation from across the global RIR and ICANN communities. In this webinar, the panelists will showcase the progress achieved so far in the ICP-2 Review. The session will also provide an introduction to the draft version of a document that aims to update ICP-2: Criteria for Establishment of New Regional Internet Registries. This updated document is titled "Governance Document for the Recognition, Maintenance, and De-recognition of Regional Internet Registries". This document is currently open for comments from 14 April to 27 May 2025. We invite community input on this draft document and encourage everyone interested in this topic to attend this session. We look forward to having your inputs in this webinar. Key Takeaways * Learn more on the progress achieved so far in the ICP-2 Review process * Gain insights into the draft version of the document that aims to update ICP-2: ?Governance Document for the Recognition, Maintenance, and De-recognition of Regional Internet Registries" * Get useful feedback from the community on the draft document Secure your spot and register here. Be sure to save the date and spread the word as your participation is key to making these sessions a success! ________________________________ Explore the full schedule and learn more about AFRINIC webinars on our Webinar Series Page. We look forward to having you join us for these insightful sessions! ________________________________ Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Thu May 8 12:40:25 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Thu, 8 May 2025 12:40:25 +0000 Subject: [rpd] The AFRINIC Webinar on "ICP-2 Review" is Streaming Shortly! Message-ID: (Apologies for cross-posting) Dear Colleagues, The webinar on "ICP-2 Review" is about to start. If you are yet to register for this webinar, please do so here. If you are unable to join us on Zoom, we will be streaming the webinar LIVE on the AFRINIC Youtube Page here. We look forward to your participation in this exciting webinar series and hope to see you there. Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Tue Jul 15 11:43:31 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Tue, 15 Jul 2025 11:43:31 +0000 Subject: [rpd] Organisation of New AFRINIC Board Elections by 30 September 2025 Message-ID: Apologies for cross-posting Dear Valued Members and the Internet Community, During the elections held on 23 June 2025, suspicions of irregularities were raised, particularly regarding the use of Powers of Attorney by some voters. Complaints were submitted to the relevant authorities by aggrieved parties, and the Police is investigating the matter. In the interest of transparency and fairness and given the absence of final conclusions from the ongoing investigation, I made the decision to annul the results of these elections. Therefore, I am currently unable to formally report on the extent of the identified irregularities. Nevertheless, I reported the matter to the Supreme Court of Mauritius and requested an extension of my mandate as Receiver to organize new elections. This request was granted. These elections must now be held no later than 30 September 2025. In this context, and to ensure a more inclusive electoral process, I invite all stakeholders of the Internet community to submit the names of credible and trustworthy individuals to serve on the Nominations Committee (NomCom), which will be responsible for overseeing the candidate selection process. The responsibilities of the Nom Com are outlined here: a) use its best effort towards ensuring that a satisfactory number of individuals from the African internet community stand as candidate for the election of the directors of AFRINIC; and b) have general responsibility for, and shall supervise the conduct of the polls by the election Committee throughout the voting period. c) In the discharge of its function above, the Nom Com: i. shall call for candidates for elections held by AFRINIC; ii. prescribe criteria and qualifications for eligibility to stand as candidate for elections held by AFRINIC; iii. may interview candidates prior to finalising the list of candidature; and d) Shall finalise the list of candidates for any election held by AFRINIC. Deadline for submission: 17 July 2025 Please send your proposals to the following email address: nomcomselection at afrinic.net The NomCom will be formed by selecting one representative from each region. This measure helps protect the integrity of the election and ensures neutrality, addressing any concerns of regional bias or conflict of interest. Finally, to prevent any disputes similar to those previously observed, neither Powers of Attorney nor proxies will be accepted for the upcoming elections. The elections will be conducted entirely online, allowing all eligible voting members to exercise their rights from wherever they are. Thank you for your cooperation and your commitment to AFRINIC?s renewal and stability. Gowtamsingh DABEE Receiver -------------- next part -------------- An HTML attachment was scrubbed... URL: From guelordshadimiadi at gmail.com Tue Jul 15 22:23:14 2025 From: guelordshadimiadi at gmail.com (BINEMO SHADIMIADI Jean Guelord) Date: Wed, 16 Jul 2025 00:23:14 +0200 Subject: [rpd] RPD Digest, Vol 211, Issue 1 In-Reply-To: References: Message-ID: La fraude ?lectorale doit se faire sous plusieurs aspects : 1. Aspects proc?durale : si le comit? d'organisation n'ont pas respect? la proc?dure en cette mati?re. 2 . Au niveau des candidats 3. Au niveau des ?lecteurs. Ce pourquoi nous posons quelques questions ? la commission et la communaut? enti?re : 1. Vous avez fait annuler les ?lections sur base de soup?onne ! Puisque vous ?tes incapable de donner le conclusion de l'enqu?te selon vos dire? ?tes vous a mesure de nous rassurer si cette enqu?te ?tait il ind?pendant et inclusives ? 2. Les ?lections annul?s et vous r?organiser les ?lections ! Quelles sont les pr?cautions prises jusqu'? pr?sent pour nous garantir une bonne ?lections ? Et l'environnement actuel de notre communaut? permet il l'organisation de nouvelle ?lections vu que nous venons d'une d?b?cle ?lections dont m?me la participation ?tait entach? d'irr?gularit?s ? 3. Pour l'enregistrement des ?lecteurs que faite vous ou sa reste carr? comme vous l'avez souhait? afin de concr?tiser l'objectif de la mains noir? 4.chers toutes et tous, nous observons jours et nuits comment notre communaut? se d?truisent et fait d?truit sans aucune intervention. Ce pourquoi je lance le crie d'alarme pour demander au sage de la communaut?, scientifiques et autres comp?tences au sein de notre communaut? de bien vouloir se lever pour sauver la navire. Au cas contraire nous allons nous noyer. Pour terminer l'?quipe d'organisation est encore cr?dible ? Et si oui donner le r?sultat de l'enqu?te et donner nous de proposition pouvant rendre le chose claire et efficace ou sinon ?viter nous la d?cadence. Je dit! *BINEMO SHADIMIADI Jean GuelordCoordonnateur du Secr?tariat Provincial du Volontariat,Vice Pr?sident de la F?d?ration de la Promotion du Num?rique en Afrique, pr?sident du Centre de Convergence des Entrepreneurs du CongoCoach des PMes, Micro entreprise, EntreprenantsSp?cialiste en planification, entrepreneuriat, gestion des ressources humaines et fiscalit?;Formateur senior en initiative personnel, ?ducation financi?re, gestion des projets, cr?ation et gestion des entreprises et ONG;consultant en appuie conseil et entrepreneuriatguelordshadimiadi at gmail.com +243976451362+243816536891Whatsapp+243976451362Tweeter: https://twitter.com/jbinemo?lang=fr Facebook: https://www.facebook.com/jeanguelord.binemo LinkedIn:https://www.linkedin.com/in/jean-guelord-binemo-65bb72145 https://www.instagram.com/jeanguelord/ 88, Avenue Maniema, C/ Lubumbashi, Q/Kiwele, ville de Lubumbashi, Province du Haut Katanga* Le mar. 15 juil. 2025, 14:01, a ?crit : > Send RPD mailing list submissions to > rpd at afrinic.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.afrinic.net/mailman/listinfo/rpd > or, via email, send a message with subject or body 'help' to > rpd-request at afrinic.net > > You can reach the person managing the list at > rpd-owner at afrinic.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of RPD digest..." > > > Today's Topics: > > 1. Organisation of New AFRINIC Board Elections by 30 September > 2025 (comms at afrinic.net) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Jul 2025 11:43:31 +0000 > From: "comms at afrinic.net" > To: AFRINIC Communication via RPD > Subject: [rpd] Organisation of New AFRINIC Board Elections by 30 > September 2025 > Message-ID: > < > AM5P190MB043542643A404BF7F10AA0D2A757A at AM5P190MB0435.EURP190.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="windows-1252" > > Apologies for cross-posting > > Dear Valued Members and the Internet Community, > > During the elections held on 23 June 2025, suspicions of irregularities > were raised, particularly regarding the use of Powers of Attorney by some > voters. Complaints were submitted to the relevant authorities by aggrieved > parties, and the Police is investigating the matter. > > In the interest of transparency and fairness and given the absence of > final conclusions from the ongoing investigation, I made the decision to > annul the results of these elections. Therefore, I am currently unable to > formally report on the extent of the identified irregularities. > > Nevertheless, I reported the matter to the Supreme Court of Mauritius and > requested an extension of my mandate as Receiver to organize new elections. > This request was granted. These elections must now be held no later than 30 > September 2025. > > In this context, and to ensure a more inclusive electoral process, I > invite all stakeholders of the Internet community to submit the names of > credible and trustworthy individuals to serve on the Nominations Committee > (NomCom), which will be responsible for overseeing the candidate selection > process. The responsibilities of the Nom Com are outlined here: > > a) use its best effort towards ensuring that a satisfactory number of > individuals from the African internet community stand as candidate for the > election of the directors of AFRINIC; and > > b) have general responsibility for, and shall supervise the conduct of > the polls by the election Committee throughout the voting period. > > c) In the discharge of its function above, the Nom Com: > > i. shall call for candidates for > elections held by AFRINIC; > > ii. prescribe criteria and qualifications > for eligibility to stand as candidate for elections held by AFRINIC; > > iii. may interview candidates prior to > finalising the list of candidature; and > > d) Shall finalise the list of candidates for any election held by > AFRINIC. > > Deadline for submission: 17 July 2025 > > Please send your proposals to the following email address: > nomcomselection at afrinic.net > > The NomCom will be formed by selecting one representative from each > region. This measure helps protect the integrity of the election and > ensures neutrality, addressing any concerns of regional bias or conflict of > interest. > > Finally, to prevent any disputes similar to those previously observed, > neither Powers of Attorney nor proxies will be accepted for the upcoming > elections. The elections will be conducted entirely online, allowing all > eligible voting members to exercise their rights from wherever they are. > > Thank you for your cooperation and your commitment to AFRINIC?s renewal > and stability. > > Gowtamsingh DABEE > > Receiver > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20250715/a63df465/attachment-0001.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > ------------------------------ > > End of RPD Digest, Vol 211, Issue 1 > *********************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Wed Jul 16 13:02:03 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Wed, 16 Jul 2025 13:02:03 +0000 Subject: [rpd] Deadline Extension for Nominations Committee (NomCom) Applications Message-ID: Apologies for Cross-posting Dear Valued Members and the Internet Community, To allow broader participation from the community and ensure ample time for quality NomCom submissions, the nomination deadline has been extended from 17 July 2025, as previously communicated, to 23 July 2025. The NomCom plays a critical role in the success of AFRINIC elections. Its responsibilities include: * Calling for candidates for elections held by AFRINIC. * Prescribing criteria and qualifications for eligibility to stand as candidates. * Interviewing candidates, where necessary, prior to finalising the list of candidates. * Using its best efforts to ensure a satisfactory number of qualified candidates from the African Internet community stand for election. * Overseeing and supervising the candidate selection process in collaboration with the Election Committee. We invite all stakeholders to nominate credible and trustworthy individuals to serve on the NomCom. One representative from each AFRINIC service region will be selected to ensure neutrality and regional balance. Please send your nominations to: nomcomselection at afrinic.net by 23 July 2025. Thank you for your continued support and commitment to AFRINIC?s renewal and stability. Kind Regards, Gowtamsingh DABEE Receiver, AFRINIC -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Mon Jul 21 14:04:52 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Mon, 21 Jul 2025 14:04:52 +0000 Subject: [rpd] Register for the "Behind the Ballot: Navigating the AFRINIC Election Process" Webinar on 23rd July 2025. Message-ID: {Apologies for cross-posting} Dear Colleagues, You are invited to register for the webinar on "Behind the Ballot: Navigating the AFRINIC Election Process" Webinar. * Date: Wednesday 23rd July 2025 * Time: 11:00 - 12:00 UTC * Duration: 1:00 Hr * Registration link ________________________________ What happened? * Annulment of June 2025 election due to alleged irregularities through voting by POAs which is being investigated by the Police. What has changed? * No PoAs or proxies allowed?members will designate voters directly, enhancing trust and security. * New, rigorous voter-verification procedures ensuring accurate voter identity. * Increased transparency: all voter designations published clearly online for public verification. * Stronger safeguards to guarantee accountability and fairness throughout the election cycle. Why you should attend? * Clearly understand why the previous election was annulled. * Learn in detail about the reforms AFRINIC has implemented, particularly the removal of PoAs and proxies. * Gain clarity on the entire revised 2025 election timeline, with important dates and milestones explained. Who will be speaking? * Mr. Musa Stephen HONLUE, Chair, Election Committee * Mrs. Madhvi Gokool, Election Committee Member * Mr. Kishna Dhondee, Election Committee Member * Mr. Mukom Tamon, Election Committee Member ________________________________ Act now: Register for the webinar now! After registration, you?ll receive an email with webinar details, reminders, and an opportunity to send in questions beforehand. Join us to ensure your voice is heard, help rebuild trust, and shape a stronger AFRINIC election process?one rooted in fairness, transparency, and accountability. ________________________________ Kind Regards, The 2025 Elections Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Tue Jul 29 13:13:29 2025 From: comms at afrinic.net (comms at afrinic.net) Date: Tue, 29 Jul 2025 13:13:29 +0000 Subject: [rpd] =?windows-1252?q?Register_for_the_=22Behind_the_Ballot=3A_S?= =?windows-1252?q?ecure_Your_Vote_=96_Voter_Designation_Process=22_Webinar?= =?windows-1252?q?_on_5th_August_2025=2E?= Message-ID: (Apologies for cross-posting) Dear Colleagues, You are invited to register for the webinar on "Behind the Ballot: Secure Your Vote ? Voter Designation Process" Webinar. * Date: Tuesday 5th August 2025 * Time: 11:00 - 12:00 UTC * Duration: 1:00 Hr * Registration Link As we prepare for the 2025 AFRINIC Board Election taking place on 29 August, this session will provide a comprehensive overview of the key actions your organisation must take to ensure its vote is formally designated, successfully verified, and accurately counted. >From the submission of Authorised Voter Designation forms to the identity verification process and publication of the Voters? Register, this webinar is designed to equip you with the knowledge, tools, and timelines needed to participate with confidence, transparency, and compliance in the upcoming election. ________________________________ Who will be speaking? * Mr. Musa Stephen HONLUE, Chair, Election Committee * Mr. Mukom Tamon, Election Committee Member ________________________________ Webinar Objectives * Walk Resource Members through the Voter Designation Process * Explain the roles and responsibilities involved in the Voter Designation Process * The crucial role the community can play to assist in the Voter Designation Process ________________________________ Who Should Attend: * Registered Contacts of eligible Resource Members. * The African Technical Community. Act now: Register for the Webinar Now! After registration, you?ll receive an email with webinar details, reminders, and an opportunity to send in questions beforehand. Join us to ensure your voice is heard, help rebuild trust, and shape a stronger AFRINIC election process?one rooted in fairness, transparency, and accountability. Kind Regards, The 2025 Elections Committee. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Fri Aug 15 04:26:33 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Fri, 15 Aug 2025 09:56:33 +0530 Subject: [rpd] Call for nomination of candidates for AFRINIC 2025 Board Election Message-ID: <91C272E2-6945-4D31-A711-223681CD2A66@afrinic.net> ***** Lire la version Fran?aise en bas***** Dear colleagues, The Nomination Committee 2025 (NomCom July 2025) is pleased to announce the opening of nominations for candidates in the 2025 election for AFRINIC Board of Directors. The Call for nominations for candidates is open from 14 to 28 August 2025. The available seats on AFRINIC's Board of Directors for the 2025 elections are as follows: Seat One: North Africa; Seat Two: West Africa; Seat Three: Indian Ocean; Seat Four: Central Africa; Seat Five: Southern Africa; Seat Six: Eastern Africa; Seat Seven: Region-Independent; Seat Eight: Region-Independent. Each seat can only be held by one candidate. A natural person residing in the above sub-regions and national of a country in the said sub-region, as stated, may be nominated for Seats 1, 2, 3, 4, 5 and 6. A natural person residing in any of the above sub-regions and national of a country in any of the said sub-regions may be nominated for Seats 7 and 8. Elected candidates will serve a term not exceeding (3) years only with respect to Seats 1, 2, 3, 4, 5 and 6. Elected candidates will serve a term not exceeding (3) years only with respect to Seats 7 and 8. The newly seated board must, at it its first order of business and within one month of being constituted, agree on an initial distribution of term lengths in order to implement the orderly rotation of Board seats required by the bylaws The above is in accordance with Articles 13.4, 13.5, 13.6 and 13.7 of the AFRINIC Bylaws. The Call for Candidates is opened till 28 August 2025 at 23:59 UTC. You may read the Election Guidelines at: https://elections.afrinic.net/about-election-2025/election-guidelines and its related Criteria is available at: https://elections.afrinic.net/about-election-2025/election-criteria The nomination form must be completed online via the dedicated platform, and all relevant attachments must also be uploaded through the same platform at: https://forms.afrinic.net/nomination-form-2025 Visit the website https://elections.afrinic.net for more information. [Sent on behalf of Nomination Committee of July 2025] ?????????? ***** Version Fran?aise***** Chers coll?gues, Le Comit? de Nomination 2025 a le plaisir d'annoncer l'ouverture des candidatures pour l'?lection 2025 du Conseil d'Administration d'AFRINIC. L'appel ? candidatures est ouvert du 14 au 28 Ao?t 2025. Les si?ges disponibles au sein du Conseil d'Administration d'AFRINIC pour ces ?lections de 2025 sont les suivants : Si?ge Un : Afrique du Nord ; Si?ge Deux : Afrique de l'Ouest ; Si?ge Trois : Oc?an Indien ; Si?ge Quatre : Afrique Centrale ; Si?ge Cinq : Afrique Australe ; Si?ge Six : Afrique de l'Est ; Si?ge Sept : Non R?gional ; Si?ge Huit : Non R?gional. Chaque si?ge ne peut ?tre occup? que par un seul candidat. Une personne physique r?sidant dans les sous-r?gions susmentionn?es et ressortissante d'un pays de ladite sous-r?gion, comme indiqu?, peut ?tre nomm?e pour les si?ges 1, 2, 3, 4, 5 et 6. Une personne physique r?sidant dans l'une des sous-r?gions susmentionn?es et ressortissante d'un pays de l'une desdites sous-r?gions peut ?tre nomm?e pour les si?ges 7 et 8. Les candidats ?lus exerceront un mandat ne d?passant pas (3) ans en ce qui concerne les si?ges 1, 2, 3, 4, 5 et 6.Les candidats ?lus exerceront un mandat ne d?passant pas (3) ans en ce qui concerne les si?ges 7 et 8. Le nouveau conseil d'administration doit, lors de sa premi?re r?union et dans un d?lai d'un mois apr?s sa constitution, convenir d'une r?partition initiale des dur?es de mandat afin de mettre en ?uvre la rotation des si?ges du conseil d'administration requise par les statuts.Ce qui pr?c?de est conforme aux articles 13.4, 13.5, 13.6 et 13.7 des statuts d?AFRINIC. L'appel ? candidatures est ouvert jusqu'au 28 ao?t 2025 ? 23h59 UTC. Vous pouvez consulter le guide ?lectoral ? l'adresse suivante : https://elections.afrinic.net/about-election-2025/election-guidelineset les crit?res sont disponibles ? l'adresse suivante : https://elections.afrinic.net/about-election-2025/election-criteria Le formulaire de candidature doit ?tre rempli en ligne via la plateforme d?di?e, et toutes les pi?ces justificatives pertinentes doivent ?galement ?tre t?l?charg?es via la m?me plateforme ? l'adresse suivante : https://forms.afrinic.net/nomination-form-2025 Visitez le site web https://elections.afrinic.net pour plus d?informations. [Envoy? au nom du Comit? de Nomination de Juillet 2025] -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Fri Aug 15 05:44:24 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Fri, 15 Aug 2025 11:14:24 +0530 Subject: [rpd] Call for nomination of candidates for AFRINIC 2025 Board Election In-Reply-To: <91C272E2-6945-4D31-A711-223681CD2A66@afrinic.net> References: <91C272E2-6945-4D31-A711-223681CD2A66@afrinic.net> Message-ID: <4C03611D-AFD5-4487-810D-C721D7ED6252@afrinic.net> Dear colleagues, Please ignore this message as per the instructions of the Receiver. Another message on the call for nomination will follow. Regards, AFRINIC Communication > On 15 Aug 2025, at 09:56, AFRINIC Communication wrote: > > ***** Lire la version Fran?aise en bas***** > > Dear colleagues, > > The Nomination Committee 2025 (NomCom July 2025) is pleased to announce the opening of nominations for candidates in the 2025 election for AFRINIC Board of Directors. The Call for nominations for candidates is open from 14 to 28 August 2025. > > The available seats on AFRINIC's Board of Directors for the 2025 elections are as follows: > > Seat One: North Africa; > Seat Two: West Africa; > Seat Three: Indian Ocean; > Seat Four: Central Africa; > Seat Five: Southern Africa; > Seat Six: Eastern Africa; > Seat Seven: Region-Independent; > Seat Eight: Region-Independent. > > Each seat can only be held by one candidate. A natural person residing in the above sub-regions and national of a country in the said sub-region, as stated, may be nominated for Seats 1, 2, 3, 4, 5 and 6. > A natural person residing in any of the above sub-regions and national of a country in any of the said sub-regions may be nominated for Seats 7 and 8. > > Elected candidates will serve a term not exceeding (3) years only with respect to Seats 1, 2, 3, 4, 5 and 6. > > Elected candidates will serve a term not exceeding (3) years only with respect to Seats 7 and 8. > The newly seated board must, at it its first order of business and within one month of being constituted, agree on an initial distribution of term lengths in order to implement the orderly rotation of Board seats required by the bylaws > The above is in accordance with Articles 13.4, 13.5, 13.6 and 13.7 of the AFRINIC Bylaws. > > The Call for Candidates is opened till 28 August 2025 at 23:59 UTC. > > You may read the Election Guidelines at: https://elections.afrinic.net/about-election-2025/election-guidelines and its related Criteria is available at: https://elections.afrinic.net/about-election-2025/election-criteria > > The nomination form must be completed online via the dedicated platform, and all relevant attachments must also be uploaded through the same platform at: https://forms.afrinic.net/nomination-form-2025 > > Visit the website https://elections.afrinic.net for more information. > > [Sent on behalf of Nomination Committee of July 2025] > > ?????????? > > ***** Version Fran?aise***** > > Chers coll?gues, > > Le Comit? de Nomination 2025 a le plaisir d'annoncer l'ouverture des candidatures pour l'?lection 2025 du Conseil d'Administration d'AFRINIC. L'appel ? candidatures est ouvert du 14 au 28 Ao?t 2025. > > Les si?ges disponibles au sein du Conseil d'Administration d'AFRINIC pour ces ?lections de 2025 sont les suivants : > > Si?ge Un : Afrique du Nord ; > Si?ge Deux : Afrique de l'Ouest ; > Si?ge Trois : Oc?an Indien ; > Si?ge Quatre : Afrique Centrale ; > Si?ge Cinq : Afrique Australe ; > Si?ge Six : Afrique de l'Est ; > Si?ge Sept : Non R?gional ; > Si?ge Huit : Non R?gional. > > Chaque si?ge ne peut ?tre occup? que par un seul candidat. Une personne physique r?sidant dans les sous-r?gions susmentionn?es et ressortissante d'un pays de ladite sous-r?gion, comme indiqu?, peut ?tre nomm?e pour les si?ges 1, 2, 3, 4, 5 et 6. Une personne physique r?sidant dans l'une des sous-r?gions susmentionn?es et ressortissante d'un pays de l'une desdites sous-r?gions peut ?tre nomm?e pour les si?ges 7 et 8. > > Les candidats ?lus exerceront un mandat ne d?passant pas (3) ans en ce qui concerne les si?ges 1, 2, 3, 4, 5 et 6.Les candidats ?lus exerceront un mandat ne d?passant pas (3) ans en ce qui concerne les si?ges 7 et 8. > > Le nouveau conseil d'administration doit, lors de sa premi?re r?union et dans un d?lai d'un mois apr?s sa constitution, convenir d'une r?partition initiale des dur?es de mandat afin de mettre en ?uvre la rotation des si?ges du conseil d'administration requise par les statuts.Ce qui pr?c?de est conforme aux articles 13.4, 13.5, 13.6 et 13.7 des statuts d?AFRINIC. > > L'appel ? candidatures est ouvert jusqu'au 28 ao?t 2025 ? 23h59 UTC. > > Vous pouvez consulter le guide ?lectoral ? l'adresse suivante : https://elections.afrinic.net/about-election-2025/election-guidelineset les crit?res sont disponibles ? l'adresse suivante : https://elections.afrinic.net/about-election-2025/election-criteria > > Le formulaire de candidature doit ?tre rempli en ligne via la plateforme d?di?e, et toutes les pi?ces justificatives pertinentes doivent ?galement ?tre t?l?charg?es via la m?me plateforme ? l'adresse suivante : https://forms.afrinic.net/nomination-form-2025 > > Visitez le site web https://elections.afrinic.net pour plus d?informations. > > [Envoy? au nom du Comit? de Nomination de Juillet 2025] -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Fri Aug 15 08:01:36 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Fri, 15 Aug 2025 13:31:36 +0530 Subject: [rpd] Call for nomination of candidates for AFRINIC 2025 Board Election Message-ID: ***** Lire la version Fran?aise en bas***** Dear colleagues, The Nomination Committee 2025 (NomCom July 2025) is pleased to announce the opening of nominations for candidates in the 2025 election for AFRINIC Board of Directors. The Call for nominations for candidates is open from 14 to 28 August 2025. The available seats on AFRINIC's Board of Directors for the 2025 elections are as follows: Seat One: North Africa; Seat Two: West Africa; Seat Three: Indian Ocean; Seat Four: Central Africa; Seat Five: Southern Africa; Seat Six: Eastern Africa; Seat Seven: Region-Independent; Seat Eight: Region-Independent. Each seat can only be held by one candidate. A natural person residing in the above sub-regions and national of a country in the said sub-region, as stated, may be nominated for Seats 1, 2, 3, 4, 5 and 6. A natural person residing in any of the above sub-regions and national of a country in any of the said sub-regions may be nominated for Seats 7 and 8. Elected candidates will serve a term not exceeding (3) years only with respect to Seats 1, 2, 3, 4, 5 and 6. Elected candidates will serve a term not exceeding (3) years only with respect to Seats 7 and 8. The Call for Candidates is opened till 28 August 2025 at 23:59 UTC. You may read the Election Guidelines at: https://elections.afrinic.net/about-election-2025/election-guidelines and its related Criteria is available at: https://elections.afrinic.net/about-election-2025/election-criteria The nomination form must be completed online via the dedicated platform, and all relevant attachments must also be uploaded through the same platform at: https://forms.afrinic.net/nomination-form-2025 Visit the website https://elections.afrinic.net for more information. [Sent on behalf of Nomination Committee of July 2025] ?????????? ***** Version Fran?aise***** Chers coll?gues, Le Comit? de Nomination 2025 a le plaisir d'annoncer l'ouverture des candidatures pour l'?lection 2025 du Conseil d'Administration d'AFRINIC. L'appel ? candidatures est ouvert du 14 au 28 Ao?t 2025. Les si?ges disponibles au sein du Conseil d'Administration d'AFRINIC pour ces ?lections de 2025 sont les suivants : Si?ge Un : Afrique du Nord ; Si?ge Deux : Afrique de l'Ouest ; Si?ge Trois : Oc?an Indien ; Si?ge Quatre : Afrique Centrale ; Si?ge Cinq : Afrique Australe ; Si?ge Six : Afrique de l'Est ; Si?ge Sept : Non R?gional ; Si?ge Huit : Non R?gional. Chaque si?ge ne peut ?tre occup? que par un seul candidat. Une personne physique r?sidant dans les sous-r?gions susmentionn?es et ressortissante d'un pays de ladite sous-r?gion, comme indiqu?, peut ?tre nomm?e pour les si?ges 1, 2, 3, 4, 5 et 6. Une personne physique r?sidant dans l'une des sous-r?gions susmentionn?es et ressortissante d'un pays de l'une desdites sous-r?gions peut ?tre nomm?e pour les si?ges 7 et 8. Les candidats ?lus exerceront un mandat ne d?passant pas (3) ans en ce qui concerne les si?ges 1, 2, 3, 4, 5 et 6.Les candidats ?lus exerceront un mandat ne d?passant pas (3) ans en ce qui concerne les si?ges 7 et 8. L'appel ? candidatures est ouvert jusqu'au 28 ao?t 2025 ? 23h59 UTC. Vous pouvez consulter le guide ?lectoral ? l'adresse suivante : https://elections.afrinic.net/about-election-2025/election-guidelineset les crit?res sont disponibles ? l'adresse suivante : https://elections.afrinic.net/about-election-2025/election-criteria Le formulaire de candidature doit ?tre rempli en ligne via la plateforme d?di?e, et toutes les pi?ces justificatives pertinentes doivent ?galement ?tre t?l?charg?es via la m?me plateforme ? l'adresse suivante : https://forms.afrinic.net/nomination-form-2025 Visitez le site web https://elections.afrinic.net pour plus d?informations. [Envoy? au nom du Comit? de Nomination de Juillet 2025] -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Tue Aug 19 11:17:50 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Tue, 19 Aug 2025 16:47:50 +0530 Subject: [rpd] Board Election Nomination Form Now Available Message-ID: Dear Resource Members, We are pleased to inform you that the online nomination form for the Board Election s now fully functional following important content updates. We encourage you to proceed with the nomination of candidates. As part of these updates, please note the following: The nomination form is available at: https://forms.afrinic.net/nomination-form-2025 The election platform has been updated with the new election timeline at: https://elections.afrinic.net/ We apologise for any inconvenience caused during the maintenance period and appreciate your understanding. Best regards, AFRINIC Communications -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Tue Aug 19 11:21:54 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Tue, 19 Aug 2025 16:51:54 +0530 Subject: [rpd] Board Election Nomination Form Now Available Message-ID: <0DB86314-3A67-4044-B7BD-D7C27C27AD10@afrinic.net> Dear Resource and Community Members, We are pleased to inform you that the online nomination form for the Board Election s now fully functional following important content updates. We encourage you to proceed with the nomination of candidates. As part of these updates, please note the following: The nomination form is available at: https://forms.afrinic.net/nomination-form-2025 The election platform has been updated with the new election timeline at: https://elections.afrinic.net/ We apologise for any inconvenience caused during the maintenance period and appreciate your understanding. Best regards, AFRINIC Communications -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Tue Aug 26 13:05:41 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Tue, 26 Aug 2025 17:05:41 +0400 Subject: [rpd] Reminder: Call for Nominations for candidates in the 2025 election is still Open Message-ID: <8D3D5705-67CD-4C72-939C-A0FD03004703@afrinic.net> Dear Resource and Community Members, The Call for Nominations for candidates in the 2025 election for AFRINIC Board of Directors is open till 29 August 2025 at 23:59 Mauritius time. We also encourage those who have previously submitted applications in the last process to resubmit their applications. The available seats on AFRINIC's Board of Directors for the 2025 elections are as follows: Seat One: North Africa; Seat Two: West Africa; Seat Three: Indian Ocean; Seat Four: Central Africa; Seat Five: Southern Africa; Seat Six: Eastern Africa; Seat Seven: Region-Independent; Seat Eight: Region-Independent. Each seat can only be held by one candidate. A natural person residing in the above sub-regions and national of a country in the said sub-region, as stated, may be nominated for Seats 1, 2, 3, 4, 5 and 6. A natural person residing in any of the above sub-regions and national of a country in any of the said sub-regions may be nominated for Seats 7 and 8. Elected candidates will serve a term not exceeding (3) years only with respect to Seats 1, 2, 3, 4, 5 and 6. Elected candidates will serve a term not exceeding (3) years only with respect to Seats 7 and 8. The Call for Candidates is open till 29 August 2025 at 23:59 MUT. You may read the Election Guidelines (https://elections.afrinic.net/about-election-2025/election-guidelines) and its related Criteria (https://elections.afrinic.net/about-election-2025/election-criteria). The nomination form (https://forms.afrinic.net/nomination-form-2025) must be completed online via the dedicated platform, and all relevant attachments must also be uploaded through the same platform (https://forms.afrinic.net/nomination-form-2025). Visit the Election Portal (https://elections.afrinic.net/) for more information. Kind regards, Mrs Hadia El Miniawi Chairperson Nomination Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Fri Aug 29 09:26:04 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Fri, 29 Aug 2025 13:26:04 +0400 Subject: [rpd] AFRINIC Board Election: Deadline extension for the Call for candidates Message-ID: <1D607A77-8AD2-4543-BB10-5D5D51B6A0AE@afrinic.net> Dear Resource and Community Members, We are pleased to announce the extension of the call for candidates for the AFRINIC Board Election to Tuesday, 2 September 2025 at 23:59 MUT . We encourage you to submit nominations for the following open Board positions. Seat One: North Africa; Seat Two: West Africa; Seat Three: Indian Ocean; Seat Four: Central Africa; Seat Five: Southern Africa; Seat Six: Eastern Africa; Seat Seven: Region-Independent; Seat Eight: Region-Independent. Nominations can be submitted through our online forms: https://forms.afrinic.net/nomination-form-2025 As a reminder, all candidate nominations should be accompanied by a corresponding support letter from both the nominating organisation and seconding organisation respectively. For Seats 1?6 The nominator must be from the same country as the candidate. The seconder must be from the same subregion as the candidate. For Seats 7?8 The nominator must be from the same country as the candidate. The seconder may be from any AFRINIC region. Important Information about Nominating Organisation and Seconding Organisation to assist prospective candidates in the submission of the candidature We are providing two templates for candidates to adopt. The nominator is required to submit a supporting letter as per the Template (PDF) - https://forms.afrinic.net/images/election/Nominating_Letter_English_Version.pdf The seconder is required to submit a supporting letter as per the Template (PDF) - https://forms.afrinic.net/images/election/Seconding_Letter_English_version.pdf Individuals who have already submitted their candidature are invited to ensure that their corresponding supporting letters cover the gist of the aforementioned template letters provided. In case they do not, they are requested to submit fresh supporting letters directly to nomcom25 at afrinic.net We look forward to receiving your nominations. Mrs Hadia Elminiawi Chairperson Nomination Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at tinka.africa Sun Aug 31 13:52:00 2025 From: mark at tinka.africa (Mark Tinka) Date: Sun, 31 Aug 2025 15:52:00 +0200 Subject: [rpd] APRICOT 2026: Call for Volunteers (Programme Committee) Message-ID: <4be5b0c3-79cf-4554-9af4-928443dc66c6@tinka.africa> Hello all. The APRICOT 2026 Organising Committee would like to welcome everyone to join us in Jakarta, Indonesia, from 5th - 12th February 2026. The APRICOT 2026 PC (Programme Committee) is responsible for the solicitation and selection of suitable presentations and tutorial content for the APRICOT 2026 conference (https://2026.apricot.net/). We are now seeking VOLUNTEERS from the community to join the APRICOT 2026 PC to assist with the development of the programme for APRICOT 2026. Eligible PC candidates must have attended recent APRICOT events, be active members of their local NOG (Network Operators Group) in the Asia Pacific region, have broad technical knowledge of Internet operations, and have good familiarity with the format of APRICOT. Having constructive opinions and ideas about how the programme content might be improved is of high value too. PC members are expected to work very actively to solicit content, follow-through with speaker updates and review submissions for technical merit. The PC meets by conference call, weekly in frequency during the three months prior to APRICOT. While participation in the weekly calls is not obligatory, active participation in content reviews is required at all times to help the PC reach consensus. PC members who are unable to fully participate in the programme development will be excused from the PC. If you are interested in joining the PC and meet the above eligibility criteria, please send a brief note to "pc-chairs at apricot.net". The note must include affiliation (if any) and a brief description about why you would make a good addition to the PC. The PC Chairs will accept nominations received by 17:00hrs UTC+8 on Sunday 7th September 2025, and will announce the new PC shortly thereafter. Many thanks! Mark Tinka, Achie Atienza & Mark Duffell APRICOT 2026 Programme Committee Chairs -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Fri Oct 3 17:10:52 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Fri, 3 Oct 2025 17:10:52 +0000 Subject: [rpd] Board Announcement: Appointment of Chairman and Vice-Chairman Message-ID: <53C90B9C-BDFD-47FD-902F-02810D484033@afrinic.net> Dear colleagues, The AFRINIC Board of Directors is pleased to announce the appointment of Prof. Adewale Adedokun as Chairman of the Board and Prof. Aziz Hilali as Vice-Chairman. These appointments were made following the Board?s election held on 12 September 2025. While this announcement comes later than anticipated, the Board wishes to reassure the community that it has been actively working to ensure continuity, stability, and effective governance during this period of transition and with the close collaboration of the Receiver, Mr Gowtamsingh Dabee. The Board takes this opportunity to sincerely thank AFRINIC members and stakeholders for their continued trust, patience, and support. We have well taken note of all the goodwill messages and expressions of collaboration. Your engagement remains vital as we work together to strengthen AFRINIC and serve the African Internet community. The Board looks forward to working under the leadership of Prof. Adedokun and Prof. Hilali in advancing AFRINIC?s mission and addressing the important challenges ahead, in close collaboration with our members and stakeholders. AFRINIC BOARD AND THE RECEIVER From sami.salih at outlook.com Mon Oct 6 05:45:27 2025 From: sami.salih at outlook.com (Sami Salih) Date: Mon, 6 Oct 2025 05:45:27 +0000 Subject: [rpd] Call for Action: Modernizing the AFRINIC Policy Manual Message-ID: Dear PDWG Community, I hope this message finds you well. I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: Previous PDWG Co-Chairs While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. AFRINIC Board We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. PDWG Community Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. With Regards. Sami Salih, PhD (ICT), PMP? Assistant Professor, Sudan University of Science and Technology Tel: (249) 122045707 -------------- next part -------------- An HTML attachment was scrubbed... URL: From benson_muite at emailplus.org Mon Oct 6 08:12:44 2025 From: benson_muite at emailplus.org (Benson Muite) Date: Mon, 06 Oct 2025 11:12:44 +0300 Subject: [rpd] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: Message-ID: <67cd5e8f-3951-4a40-94df-e1bdeacb79c2@app.fastmail.com> On Mon, Oct 6, 2025, at 8:45 AM, Sami Salih wrote: > Dear PDWG Community, > > I hope this message finds you well. > > I would like to take this opportunity to congratulate you all on the > successful election Due to the choice of voting platform, we do not know if the results announced were what was voted for by eligible Afrinic members. For electronic voting, countries such as Switzerland enforce by law that the voting platform is free and open source software to give high confidence in the integrity of announced results. The efforts to revive Afrinic are great, but a good first step is to acknowledge shortcomings so that they can be fixed if possible. >of the AFRINIC Board and the resumption of its > proper functioning. This milestone marks an important step toward > restoring stability, trust, and continuity in AFRINIC?s role as the > Regional Internet Registry for Africa. With governance now back on > track, it is the right moment to resume the Policy Development Process > (PDP) and address the policy gaps that have accumulated during the past > three years of interruption. > > As you are aware, over the past three years AFRINIC has gone through a > period of limited functionality, and the Policy Development Process > (PDP) has been effectively paused. During this time, the global > Internet number community has continued to evolve, with significant > policy updates taking place across the other RIRs. This has created a > widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and > those of our sister RIRs. > > In order to restore the momentum of policy development in our region > and to ensure that AFRINIC?s policy environment remains relevant, > consistent, and globally aligned, I would like to highlight the > following areas where action is needed: > > Previous PDWG Co-Chairs > While their terms have now ended, we request that the most recent PDWG > Co-Chairs prepare a short report summarizing the last set of policy > proposals that were under discussion before the process stalled. We > further encourage the original authors of those drafts to resubmit them > for renewed community review, or alternatively, invite any community > member to take initiative to re-submit and champion them. > > AFRINIC Board > We call on the Board to formally publish a community call for > modernizing the AFRINIC Policy Manual. This would include identifying > and prioritizing areas where policy alignment with other RIRs is needed > (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI > adoption, Whois/privacy reforms, and membership/resource governance > models). Such a call would help set a clear direction and provide > legitimacy to the process of catching up with global best practices. > > PDWG Community > Most importantly, we urge all community members to actively re-engage > in the PDP by discussing any submitted proposals, providing > constructive feedback, and enriching the drafts with insights drawn > from operational experience. The strength of AFRINIC?s PDP has always > been rooted in the diversity and expertise of its community, and your > participation will be crucial in shaping the future of Internet number > resource management in our region. > > This is a collective responsibility, and now is the right moment to > re-energize our PDP and demonstrate the resilience of the AFRINIC > community. > > With Regards. > > Sami Salih, PhD (ICT), PMP? > Assistant Professor, Sudan University of Science and Technology > Tel: (249) 122045707 > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd From ben.roberts at afrinic.net Wed Oct 8 21:57:54 2025 From: ben.roberts at afrinic.net (Ben Roberts - AfriNIC) Date: Wed, 8 Oct 2025 23:57:54 +0200 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: Message-ID: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> Sami, Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? Kind regards Ben Sent from my iPhone > On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: > > ? > Dear PDWG Community, > > I hope this message finds you well. > > I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. > > As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. > > In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: > > Previous PDWG Co-Chairs > While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. > > AFRINIC Board > We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. > > PDWG Community > Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. > > This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. > > With Regards. > > Sami Salih, PhD (ICT), PMP? > Assistant Professor, Sudan University of Science and Technology > Tel: (249) 122045707 > _______________________________________________ > Board mailing list -- board at afrinic.net > To unsubscribe send an email to board-leave at afrinic.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From seun.ojedeji at gmail.com Wed Oct 8 23:02:05 2025 From: seun.ojedeji at gmail.com (Seun Ojedeji) Date: Wed, 8 Oct 2025 19:02:05 -0400 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> Message-ID: Hello Ben, RPD It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner Regards ---- Sent from my mobile kindly excuse typos On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, wrote: > Sami, > Thanks for your mail and we appreciate your contributions to PWDG to date > and are happy to see you are keen to start it up again. I am replying as a > community member, though I am also a board member of AfriNIC. > > I feel that as we restart the PWDG process, what is absolutely key is that > we get *much more* diversity in that process. My question back to you is > to ask, how do we invigorate the process to involve many more key experts > in the digital economy of Africa? > > Kind regards > Ben > > Sent from my iPhone > > On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: > > ? > *Dear PDWG Community,* > > I hope this message finds you well. > > I would like to take this opportunity to congratulate you all on the > successful election of the AFRINIC Board and the resumption of its proper > functioning. This milestone marks an important step toward restoring > stability, trust, and continuity in AFRINIC?s role as the Regional Internet > Registry for Africa. With governance now back on track, it is the right > moment to resume the Policy Development Process (PDP) and address the > policy gaps that have accumulated during the past three years of > interruption. > > As you are aware, over the past three years AFRINIC has gone through a > period of limited functionality, and the Policy Development Process (PDP) > has been effectively paused. During this time, the global Internet number > community has continued to evolve, with significant policy updates taking > place across the other RIRs. This has created a widening gap between > AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. > > In order to restore the momentum of policy development in our region and > to ensure that AFRINIC?s policy environment remains relevant, consistent, > and globally aligned, I would like to highlight the following areas where > action is needed: > > *Previous PDWG Co-Chairs* > While their terms have now ended, we request that the most recent PDWG > Co-Chairs prepare a short report summarizing the last set of policy > proposals that were under discussion before the process stalled. We further > encourage the original authors of those drafts to resubmit them for renewed > community review, or alternatively, invite any community member to take > initiative to re-submit and champion them. > > *AFRINIC Board* > We call on the Board to formally publish a community call for modernizing > the AFRINIC Policy Manual. This would include identifying and prioritizing > areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer > frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, > and membership/resource governance models). Such a call would help set a > clear direction and provide legitimacy to the process of catching up with > global best practices. > > *PDWG Community* > Most importantly, we urge all community members to actively re-engage in > the PDP by discussing any submitted proposals, providing constructive > feedback, and enriching the drafts with insights drawn from operational > experience. The strength of AFRINIC?s PDP has always been rooted in the > diversity and expertise of its community, and your participation will be > crucial in shaping the future of Internet number resource management in our > region. > > This is a collective responsibility, and now is the right moment to > re-energize our PDP and demonstrate the resilience of the AFRINIC community. > > With Regards. > > *Sami Salih*, PhD (ICT), PMP? > Assistant Professor, Sudan University of Science and Technology > Tel: (249) 122045707 > _______________________________________________ > Board mailing list -- board at afrinic.net > To unsubscribe send an email to board-leave at afrinic.net > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Wed Oct 8 23:23:54 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Wed, 8 Oct 2025 17:23:54 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> Message-ID: <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> HI Seun, all, Fully agree with your view. I will add 2 more points: 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. Tks! Saludos, Jordi @jordipalet > El 8 oct 2025, a las 17:02, Seun Ojedeji escribi?: > > Hello Ben, RPD > > It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: > > 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. > > 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. > > 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner > > Regards > > ---- > Sent from my mobile > kindly excuse typos > > On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >> Sami, >> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >> >> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >> >> Kind regards >> Ben >> >> Sent from my iPhone >> >>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>> >>> ? >>> Dear PDWG Community, >>> >>> I hope this message finds you well. >>> >>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>> >>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>> >>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>> >>> Previous PDWG Co-Chairs >>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>> >>> AFRINIC Board >>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>> >>> PDWG Community >>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>> >>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>> >>> With Regards. >>> >>> Sami Salih, PhD (ICT), PMP? >>> Assistant Professor, Sudan University of Science and Technology >>> Tel: (249) 122045707 >>> _______________________________________________ >>> Board mailing list -- board at afrinic.net >>> To unsubscribe send an email to board-leave at afrinic.net >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From muyiwacaleb at gmail.com Thu Oct 9 00:07:19 2025 From: muyiwacaleb at gmail.com (Caleb Ogundele) Date: Wed, 8 Oct 2025 19:07:19 -0500 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: Hi Jordi and All, I'm happy this list is becoming more active, and it is a good thing. Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. *Caleb Ogundele* *Speaking for myself as a community member* On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD wrote: > HI Seun, all, > > Fully agree with your view. I will add 2 more points: > > 1) There are several policy proposals that reached consensus and are > ?paused? just waiting for the board ratification. I understand the board > will be very busy, but the ratification is basically an administrative task > that should not take too much time. So please, consider doing so ASAP, so > the implementation can also be initiated, as I think in some cases it may > take long time. > > 2) Some of use may need to plan ahead, and buy our flights as early as > possible (too close to the meeting become extremely expensive when > traveling from abroad) for the next PPM, so it will be good to announce > firm dates and location as soon as possible. > > Those that have policy proposals still under discussion really need to > have a status summary and specially understand if the actual co-chairs will > continue as suggested, so we can restart our work and encourage discussions > in the community. > > Finally, I don?t think we need a ?complete modernization of the policy > manual?, but instead concentrate in review the existing discussion and > decide if we need to focus on any new topic at the time being. > > Tks! > > Saludos, > Jordi > > @jordipalet > > > El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: > > Hello Ben, RPD > > It's good that this discussion is starting up. I don't think anything > revolutionary with the rpd needs to happen from the board level at this > time. The rpd itself should evolve through policies and while the board > indeed has the ability to write a policy when required and in > certain circumstances i do think that it isn't necessary at this time. I > would suggest the following: > > 1. Current Co-Chairs continue in their role towards the next Public Policy > Meeting (PPM) and they should coordinate on the things Sami mentioned with > regards to authors representing their proposal and new proposals as > applicable. > > 2. We usually hold 2 PPMs every year 1 during the AIS and another at the > second AFRINIC pubic meeting in the year, it will be good for the Board to > provide the rpd with some information on how soon that can happen. > > 3. With the recent board election, staff does have significant experience > on conducting credible and verifiable election. The Board should leverage > on that to organise election of Co-Chairs at the next ppm inline with the > CPM. The 2 seats should be filled in a staggered manner > > Regards > > ---- > Sent from my mobile > kindly excuse typos > > On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, < > rpd at afrinic.net> wrote: > >> Sami, >> Thanks for your mail and we appreciate your contributions to PWDG to date >> and are happy to see you are keen to start it up again. I am replying as a >> community member, though I am also a board member of AfriNIC. >> >> I feel that as we restart the PWDG process, what is absolutely key is >> that we get *much more* diversity in that process. My question back to >> you is to ask, how do we invigorate the process to involve many more key >> experts in the digital economy of Africa? >> >> Kind regards >> Ben >> >> Sent from my iPhone >> >> On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: >> >> ? >> *Dear PDWG Community,* >> >> I hope this message finds you well. >> >> I would like to take this opportunity to congratulate you all on the >> successful election of the AFRINIC Board and the resumption of its proper >> functioning. This milestone marks an important step toward restoring >> stability, trust, and continuity in AFRINIC?s role as the Regional Internet >> Registry for Africa. With governance now back on track, it is the right >> moment to resume the Policy Development Process (PDP) and address the >> policy gaps that have accumulated during the past three years of >> interruption. >> >> As you are aware, over the past three years AFRINIC has gone through a >> period of limited functionality, and the Policy Development Process (PDP) >> has been effectively paused. During this time, the global Internet number >> community has continued to evolve, with significant policy updates taking >> place across the other RIRs. This has created a widening gap between >> AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >> >> In order to restore the momentum of policy development in our region and >> to ensure that AFRINIC?s policy environment remains relevant, consistent, >> and globally aligned, I would like to highlight the following areas where >> action is needed: >> >> *Previous PDWG Co-Chairs* >> While their terms have now ended, we request that the most recent PDWG >> Co-Chairs prepare a short report summarizing the last set of policy >> proposals that were under discussion before the process stalled. We further >> encourage the original authors of those drafts to resubmit them for renewed >> community review, or alternatively, invite any community member to take >> initiative to re-submit and champion them. >> >> *AFRINIC Board* >> We call on the Board to formally publish a community call for modernizing >> the AFRINIC Policy Manual. This would include identifying and prioritizing >> areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer >> frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, >> and membership/resource governance models). Such a call would help set a >> clear direction and provide legitimacy to the process of catching up with >> global best practices. >> >> *PDWG Community* >> Most importantly, we urge all community members to actively re-engage in >> the PDP by discussing any submitted proposals, providing constructive >> feedback, and enriching the drafts with insights drawn from operational >> experience. The strength of AFRINIC?s PDP has always been rooted in the >> diversity and expertise of its community, and your participation will be >> crucial in shaping the future of Internet number resource management in our >> region. >> >> This is a collective responsibility, and now is the right moment to >> re-energize our PDP and demonstrate the resilience of the AFRINIC community. >> >> With Regards. >> >> *Sami Salih*, PhD (ICT), PMP? >> Assistant Professor, Sudan University of Science and Technology >> Tel: (249) 122045707 >> _______________________________________________ >> Board mailing list -- board at afrinic.net >> To unsubscribe send an email to board-leave at afrinic.net >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -- *Caleb Ogundele* Email: muyiwacaleb at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Thu Oct 9 00:15:22 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Wed, 8 Oct 2025 18:15:22 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: Hi Caleb, The proposals that I refer: 1) Already reached consensus. 2) Already were sent to the board with the relevant reports. So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. Saludos, Jordi @jordipalet > El 8 oct 2025, a las 18:07, Caleb Ogundele escribi?: > > Hi Jordi and All, > > I'm happy this list is becoming more active, and it is a good thing. > Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." > Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. > > Caleb Ogundele > Speaking for myself as a community member > > > > > > On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >> HI Seun, all, >> >> Fully agree with your view. I will add 2 more points: >> >> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >> > >> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >> >> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >> >> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >> >> Tks! >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>> >>> Hello Ben, RPD >>> >>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>> >>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>> >>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>> >>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>> >>> Regards >>> >>> ---- >>> Sent from my mobile >>> kindly excuse typos >>> >>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>>> Sami, >>>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>>> >>>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>>> >>>> Kind regards >>>> Ben >>>> >>>> Sent from my iPhone >>>> >>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>>> >>>>> ? >>>>> Dear PDWG Community, >>>>> >>>>> I hope this message finds you well. >>>>> >>>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>>> >>>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>> >>>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>>> >>>>> Previous PDWG Co-Chairs >>>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>>> >>>>> AFRINIC Board >>>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>>> >>>>> PDWG Community >>>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>>> >>>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>> >>>>> With Regards. >>>>> >>>>> Sami Salih, PhD (ICT), PMP? >>>>> Assistant Professor, Sudan University of Science and Technology >>>>> Tel: (249) 122045707 >>>>> _______________________________________________ >>>>> Board mailing list -- board at afrinic.net >>>>> To unsubscribe send an email to board-leave at afrinic.net >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > > > -- > Caleb Ogundele > Email: muyiwacaleb at gmail.com ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From emmanuelvitus at gmail.com Thu Oct 9 00:21:08 2025 From: emmanuelvitus at gmail.com (Emmanuel Vitus) Date: Thu, 9 Oct 2025 00:21:08 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: Good to see the list active again. Hopefully we can keep the energy focused this time and not fall back into the long circular debates we had in the past. It could help to have a simple matrix showing which proposals can be ratified quickly with little or no cost and which ones may need more time or legal review. A timeline would also be useful to follow progress taking into account the Board comments and the steps before ratification. The transfer policy should move forward as soon as possible, my 2cents. Cheers! - Emmanuel Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD a ?crit : > Hi Caleb, > > The proposals that I refer: > 1) Already reached consensus. > 2) Already were sent to the board with the relevant reports. > > So from that perspective, with ?basically administrative? I mean that > there is not ?a lot of other? work to be done in the proposals. Of course, > the board should make sure that the proposals aren?t against the company, > but the legal implications, operational feasibility, alignment with the > bylaws, etc., was already done because all this is part of the analysis > impact that was prepared *before* declaring consensus. This is just the way > the PDP works, so we aren?t changing anything. > > Saludos, > Jordi > > @jordipalet > > > El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: > > Hi Jordi and All, > > I'm happy this list is becoming more active, and it is a good thing. > Responding to @Jordi, I must respectfully differ with Jordi on point one. > While I share the desire to see pending proposals move forward, I don't > believe board ratification should be characterized as "basically an > administrative task that should not take too much time." > > Board ratification is a critical governance checkpoint where proposals are > reviewed for legal implications, operational feasibility, and alignment > with AFRINIC's mission and bylaws. Given that we're emerging from three > years of limited functionality as a community, I believe the Community and > the Board deserve adequate time to properly review and ratify proposals, > especially those that may have significant operational or financial > implications for AFRINIC and its members. Times have changed in the last > three years and community members have different views on certain policies. > Rushing this process could lead to oversights that create problems down the > line. Quality should take precedence over speed. > *Caleb Ogundele* > > > > > > *Speaking for myself as a community member* > > On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: > >> HI Seun, all, >> >> Fully agree with your view. I will add 2 more points: >> >> 1) There are several policy proposals that reached consensus and are >> ?paused? just waiting for the board ratification. I understand the board >> will be very busy, but the ratification is basically an administrative task >> that should not take too much time. So please, consider doing so ASAP, so >> the implementation can also be initiated, as I think in some cases it may >> take long time. >> >> > 2) Some of use may need to plan ahead, and buy our flights as early as >> possible (too close to the meeting become extremely expensive when >> traveling from abroad) for the next PPM, so it will be good to announce >> firm dates and location as soon as possible. >> >> Those that have policy proposals still under discussion really need to >> have a status summary and specially understand if the actual co-chairs will >> continue as suggested, so we can restart our work and encourage discussions >> in the community. >> >> Finally, I don?t think we need a ?complete modernization of the policy >> manual?, but instead concentrate in review the existing discussion and >> decide if we need to focus on any new topic at the time being. >> >> Tks! >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >> El 8 oct 2025, a las 17:02, Seun Ojedeji >> escribi?: >> >> Hello Ben, RPD >> >> It's good that this discussion is starting up. I don't think anything >> revolutionary with the rpd needs to happen from the board level at this >> time. The rpd itself should evolve through policies and while the board >> indeed has the ability to write a policy when required and in >> certain circumstances i do think that it isn't necessary at this time. I >> would suggest the following: >> >> 1. Current Co-Chairs continue in their role towards the next Public >> Policy Meeting (PPM) and they should coordinate on the things Sami >> mentioned with regards to authors representing their proposal and new >> proposals as applicable. >> >> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the >> second AFRINIC pubic meeting in the year, it will be good for the Board to >> provide the rpd with some information on how soon that can happen. >> >> 3. With the recent board election, staff does have significant experience >> on conducting credible and verifiable election. The Board should leverage >> on that to organise election of Co-Chairs at the next ppm inline with the >> CPM. The 2 seats should be filled in a staggered manner >> >> Regards >> >> ---- >> Sent from my mobile >> kindly excuse typos >> >> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, < >> rpd at afrinic.net> wrote: >> >>> Sami, >>> Thanks for your mail and we appreciate your contributions to PWDG to >>> date and are happy to see you are keen to start it up again. I am replying >>> as a community member, though I am also a board member of AfriNIC. >>> >>> I feel that as we restart the PWDG process, what is absolutely key is >>> that we get *much more* diversity in that process. My question back to >>> you is to ask, how do we invigorate the process to involve many more key >>> experts in the digital economy of Africa? >>> >>> Kind regards >>> Ben >>> >>> Sent from my iPhone >>> >>> On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: >>> >>> ? >>> *Dear PDWG Community,* >>> >>> I hope this message finds you well. >>> >>> I would like to take this opportunity to congratulate you all on the >>> successful election of the AFRINIC Board and the resumption of its proper >>> functioning. This milestone marks an important step toward restoring >>> stability, trust, and continuity in AFRINIC?s role as the Regional Internet >>> Registry for Africa. With governance now back on track, it is the right >>> moment to resume the Policy Development Process (PDP) and address the >>> policy gaps that have accumulated during the past three years of >>> interruption. >>> >>> As you are aware, over the past three years AFRINIC has gone through a >>> period of limited functionality, and the Policy Development Process (PDP) >>> has been effectively paused. During this time, the global Internet number >>> community has continued to evolve, with significant policy updates taking >>> place across the other RIRs. This has created a widening gap between >>> AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>> >>> In order to restore the momentum of policy development in our region and >>> to ensure that AFRINIC?s policy environment remains relevant, consistent, >>> and globally aligned, I would like to highlight the following areas where >>> action is needed: >>> >>> *Previous PDWG Co-Chairs* >>> While their terms have now ended, we request that the most recent PDWG >>> Co-Chairs prepare a short report summarizing the last set of policy >>> proposals that were under discussion before the process stalled. We further >>> encourage the original authors of those drafts to resubmit them for renewed >>> community review, or alternatively, invite any community member to take >>> initiative to re-submit and champion them. >>> >>> *AFRINIC Board* >>> We call on the Board to formally publish a community call for >>> modernizing the AFRINIC Policy Manual. This would include identifying and >>> prioritizing areas where policy alignment with other RIRs is needed (e.g., >>> IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, >>> Whois/privacy reforms, and membership/resource governance models). Such a >>> call would help set a clear direction and provide legitimacy to the process >>> of catching up with global best practices. >>> >>> *PDWG Community* >>> Most importantly, we urge all community members to actively re-engage in >>> the PDP by discussing any submitted proposals, providing constructive >>> feedback, and enriching the drafts with insights drawn from operational >>> experience. The strength of AFRINIC?s PDP has always been rooted in the >>> diversity and expertise of its community, and your participation will be >>> crucial in shaping the future of Internet number resource management in our >>> region. >>> >>> This is a collective responsibility, and now is the right moment to >>> re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>> >>> With Regards. >>> >>> *Sami Salih*, PhD (ICT), PMP? >>> Assistant Professor, Sudan University of Science and Technology >>> Tel: (249) 122045707 >>> _______________________________________________ >>> Board mailing list -- board at afrinic.net >>> To unsubscribe send an email to board-leave at afrinic.net >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or >> confidential. The information is intended to be for the exclusive use of >> the individual(s) named above and further non-explicilty authorized >> disclosure, copying, distribution or use of the contents of this >> information, even if partially, including attached files, is strictly >> prohibited and will be considered a criminal offense. If you are not the >> intended recipient be aware that any disclosure, copying, distribution or >> use of the contents of this information, even if partially, including >> attached files, is strictly prohibited, will be considered a criminal >> offense, so you must reply to the original sender to inform about this >> communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > > > -- > *Caleb Ogundele* > Email: muyiwacaleb at gmail.com > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From muyiwacaleb at gmail.com Thu Oct 9 00:48:53 2025 From: muyiwacaleb at gmail.com (Caleb Ogundele) Date: Wed, 8 Oct 2025 19:48:53 -0500 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: Hi Jordi, Just a reminder that we have both been co-authors of a PDP process, which means you know I have an understanding of the PDP process, as you do. On the other hand, you're absolutely right that impact analysis is conducted before consensus is declared, and I appreciate you explaining that context at least to those who might be joining the PDP process recently. The board also has the right to send it back to the community for review. However, I still believe we should be cautious about characterizing board ratification as primarily administrative, even for proposals that reached consensus before the pause. Here's why: *Context has changed significantly: *These proposals reached consensus before the three-year interruption. The operational landscape, AFRINIC's financial position, staffing capabilities, and even other RIRs have evolved during this period. The Board has a fiduciary responsibility to reassess whether the original impact analyses still hold true given current circumstances. *New Board composition:* With the recent election, we have Board members who weren't part of the original discussions around these proposals. They need adequate time to review the proposals, understand the consensus process that led to them, and ask questions if needed. Expecting quick rubber-stamping doesn't serve good governance. *Rebuilding trust requires thoroughness: *After three years of limited functionality, the community needs to see that governance processes are working properly - not just quickly. A measured, transparent review by the Board (even if it takes a bit longer) will build more confidence than rushing through ratifications. Just to be clear, I absolutely agree that these proposals should move forward; however, technology has evolved in the last three years, and other RIRs have implemented new policies that may affect other issues. However, I share your concern about the timeline. Best regards, *Caleb Ogundele**Speaking for myself as a community member* On Wed, Oct 8, 2025 at 7:24?PM jordi.palet--- via RPD wrote: > Hi Caleb, > > The proposals that I refer: > 1) Already reached consensus. > 2) Already were sent to the board with the relevant reports. > > So from that perspective, with ?basically administrative? I mean that > there is not ?a lot of other? work to be done in the proposals. Of course, > the board should make sure that the proposals aren?t against the company, > but the legal implications, operational feasibility, alignment with the > bylaws, etc., was already done because all this is part of the analysis > impact that was prepared *before* declaring consensus. This is just the way > the PDP works, so we aren?t changing anything. > > Saludos, > Jordi > > @jordipalet > > > El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: > > Hi Jordi and All, > > I'm happy this list is becoming more active, and it is a good thing. > Responding to @Jordi, I must respectfully differ with Jordi on point one. > While I share the desire to see pending proposals move forward, I don't > believe board ratification should be characterized as "basically an > administrative task that should not take too much time." > > Board ratification is a critical governance checkpoint where proposals are > reviewed for legal implications, operational feasibility, and alignment > with AFRINIC's mission and bylaws. Given that we're emerging from three > years of limited functionality as a community, I believe the Community and > the Board deserve adequate time to properly review and ratify proposals, > especially those that may have significant operational or financial > implications for AFRINIC and its members. Times have changed in the last > three years and community members have different views on certain policies. > Rushing this process could lead to oversights that create problems down the > line. Quality should take precedence over speed. > *Caleb Ogundele* > > > > > > *Speaking for myself as a community member* > > On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: > >> HI Seun, all, >> >> Fully agree with your view. I will add 2 more points: >> >> 1) There are several policy proposals that reached consensus and are >> ?paused? just waiting for the board ratification. I understand the board >> will be very busy, but the ratification is basically an administrative task >> that should not take too much time. So please, consider doing so ASAP, so >> the implementation can also be initiated, as I think in some cases it may >> take long time. >> >> > 2) Some of use may need to plan ahead, and buy our flights as early as >> possible (too close to the meeting become extremely expensive when >> traveling from abroad) for the next PPM, so it will be good to announce >> firm dates and location as soon as possible. >> >> Those that have policy proposals still under discussion really need to >> have a status summary and specially understand if the actual co-chairs will >> continue as suggested, so we can restart our work and encourage discussions >> in the community. >> >> Finally, I don?t think we need a ?complete modernization of the policy >> manual?, but instead concentrate in review the existing discussion and >> decide if we need to focus on any new topic at the time being. >> >> Tks! >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >> El 8 oct 2025, a las 17:02, Seun Ojedeji >> escribi?: >> >> Hello Ben, RPD >> >> It's good that this discussion is starting up. I don't think anything >> revolutionary with the rpd needs to happen from the board level at this >> time. The rpd itself should evolve through policies and while the board >> indeed has the ability to write a policy when required and in >> certain circumstances i do think that it isn't necessary at this time. I >> would suggest the following: >> >> 1. Current Co-Chairs continue in their role towards the next Public >> Policy Meeting (PPM) and they should coordinate on the things Sami >> mentioned with regards to authors representing their proposal and new >> proposals as applicable. >> >> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the >> second AFRINIC pubic meeting in the year, it will be good for the Board to >> provide the rpd with some information on how soon that can happen. >> >> 3. With the recent board election, staff does have significant experience >> on conducting credible and verifiable election. The Board should leverage >> on that to organise election of Co-Chairs at the next ppm inline with the >> CPM. The 2 seats should be filled in a staggered manner >> >> Regards >> >> ---- >> Sent from my mobile >> kindly excuse typos >> >> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, < >> rpd at afrinic.net> wrote: >> >>> Sami, >>> Thanks for your mail and we appreciate your contributions to PWDG to >>> date and are happy to see you are keen to start it up again. I am replying >>> as a community member, though I am also a board member of AfriNIC. >>> >>> I feel that as we restart the PWDG process, what is absolutely key is >>> that we get *much more* diversity in that process. My question back to >>> you is to ask, how do we invigorate the process to involve many more key >>> experts in the digital economy of Africa? >>> >>> Kind regards >>> Ben >>> >>> Sent from my iPhone >>> >>> On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: >>> >>> ? >>> *Dear PDWG Community,* >>> >>> I hope this message finds you well. >>> >>> I would like to take this opportunity to congratulate you all on the >>> successful election of the AFRINIC Board and the resumption of its proper >>> functioning. This milestone marks an important step toward restoring >>> stability, trust, and continuity in AFRINIC?s role as the Regional Internet >>> Registry for Africa. With governance now back on track, it is the right >>> moment to resume the Policy Development Process (PDP) and address the >>> policy gaps that have accumulated during the past three years of >>> interruption. >>> >>> As you are aware, over the past three years AFRINIC has gone through a >>> period of limited functionality, and the Policy Development Process (PDP) >>> has been effectively paused. During this time, the global Internet number >>> community has continued to evolve, with significant policy updates taking >>> place across the other RIRs. This has created a widening gap between >>> AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>> >>> In order to restore the momentum of policy development in our region and >>> to ensure that AFRINIC?s policy environment remains relevant, consistent, >>> and globally aligned, I would like to highlight the following areas where >>> action is needed: >>> >>> *Previous PDWG Co-Chairs* >>> While their terms have now ended, we request that the most recent PDWG >>> Co-Chairs prepare a short report summarizing the last set of policy >>> proposals that were under discussion before the process stalled. We further >>> encourage the original authors of those drafts to resubmit them for renewed >>> community review, or alternatively, invite any community member to take >>> initiative to re-submit and champion them. >>> >>> *AFRINIC Board* >>> We call on the Board to formally publish a community call for >>> modernizing the AFRINIC Policy Manual. This would include identifying and >>> prioritizing areas where policy alignment with other RIRs is needed (e.g., >>> IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, >>> Whois/privacy reforms, and membership/resource governance models). Such a >>> call would help set a clear direction and provide legitimacy to the process >>> of catching up with global best practices. >>> >>> *PDWG Community* >>> Most importantly, we urge all community members to actively re-engage in >>> the PDP by discussing any submitted proposals, providing constructive >>> feedback, and enriching the drafts with insights drawn from operational >>> experience. The strength of AFRINIC?s PDP has always been rooted in the >>> diversity and expertise of its community, and your participation will be >>> crucial in shaping the future of Internet number resource management in our >>> region. >>> >>> This is a collective responsibility, and now is the right moment to >>> re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>> >>> With Regards. >>> >>> *Sami Salih*, PhD (ICT), PMP? >>> Assistant Professor, Sudan University of Science and Technology >>> Tel: (249) 122045707 >>> _______________________________________________ >>> Board mailing list -- board at afrinic.net >>> To unsubscribe send an email to board-leave at afrinic.net >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or >> confidential. The information is intended to be for the exclusive use of >> the individual(s) named above and further non-explicilty authorized >> disclosure, copying, distribution or use of the contents of this >> information, even if partially, including attached files, is strictly >> prohibited and will be considered a criminal offense. If you are not the >> intended recipient be aware that any disclosure, copying, distribution or >> use of the contents of this information, even if partially, including >> attached files, is strictly prohibited, will be considered a criminal >> offense, so you must reply to the original sender to inform about this >> communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > > > -- > *Caleb Ogundele* > Email: muyiwacaleb at gmail.com > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -- *Caleb Ogundele* Email: muyiwacaleb at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Thu Oct 9 04:29:25 2025 From: sami.salih at outlook.com (Sami Salih) Date: Thu, 9 Oct 2025 04:29:25 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: Thank you all for the active participation, I truly missed this spirit of debate. If I may echo and translate Jourdi?s point: we need the Board to either ratify the proposal or return it to the list. Keeping it pending for an unnecessary period is not helping anyone. In addition, we need the Board?s decision regarding the co-chair, as it is difficult to move forward without clear leadership and facilitation for the group. I?m very glad to see things getting back on track ? Best regards, Sami Sent from Outlook for Android ________________________________ From: Caleb Ogundele Sent: Thursday, October 9, 2025 3:48:53 AM To: jordi.palet at consulintel.es Cc: rpd Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual Hi Jordi, Just a reminder that we have both been co-authors of a PDP process, which means you know I have an understanding of the PDP process, as you do. On the other hand, you're absolutely right that impact analysis is conducted before consensus is declared, and I appreciate you explaining that context at least to those who might be joining the PDP process recently. The board also has the right to send it back to the community for review. However, I still believe we should be cautious about characterizing board ratification as primarily administrative, even for proposals that reached consensus before the pause. Here's why: Context has changed significantly: These proposals reached consensus before the three-year interruption. The operational landscape, AFRINIC's financial position, staffing capabilities, and even other RIRs have evolved during this period. The Board has a fiduciary responsibility to reassess whether the original impact analyses still hold true given current circumstances. New Board composition: With the recent election, we have Board members who weren't part of the original discussions around these proposals. They need adequate time to review the proposals, understand the consensus process that led to them, and ask questions if needed. Expecting quick rubber-stamping doesn't serve good governance. Rebuilding trust requires thoroughness: After three years of limited functionality, the community needs to see that governance processes are working properly - not just quickly. A measured, transparent review by the Board (even if it takes a bit longer) will build more confidence than rushing through ratifications. Just to be clear, I absolutely agree that these proposals should move forward; however, technology has evolved in the last three years, and other RIRs have implemented new policies that may affect other issues. However, I share your concern about the timeline. Best regards, Caleb Ogundele Speaking for myself as a community member On Wed, Oct 8, 2025 at 7:24?PM jordi.palet--- via RPD > wrote: Hi Caleb, The proposals that I refer: 1) Already reached consensus. 2) Already were sent to the board with the relevant reports. So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. Saludos, Jordi @jordipalet El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: Hi Jordi and All, I'm happy this list is becoming more active, and it is a good thing. Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. Caleb Ogundele Speaking for myself as a community member On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: HI Seun, all, Fully agree with your view. I will add 2 more points: 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. Tks! Saludos, Jordi @jordipalet El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: Hello Ben, RPD It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner Regards ---- Sent from my mobile kindly excuse typos On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: Sami, Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? Kind regards Ben Sent from my iPhone On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: ? Dear PDWG Community, I hope this message finds you well. I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: Previous PDWG Co-Chairs While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. AFRINIC Board We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. PDWG Community Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. With Regards. Sami Salih, PhD (ICT), PMP? Assistant Professor, Sudan University of Science and Technology Tel: (249) 122045707 _______________________________________________ Board mailing list -- board at afrinic.net To unsubscribe send an email to board-leave at afrinic.net _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -- Caleb Ogundele Email: muyiwacaleb at gmail.com ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -- Caleb Ogundele Email: muyiwacaleb at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Thu Oct 9 04:39:11 2025 From: sami.salih at outlook.com (Sami Salih) Date: Thu, 9 Oct 2025 04:39:11 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> Message-ID: Hi Ben We already have experts from all over the world actively proposing policies and debating both online and in meeting rooms. What we need now is simply for the Board to decide on the PDWG chairs to start engaging with the community in an official way. In parallel, organizing some online sessions to the community while preparing for the upcoming AFRINIC meeting would also greatly help in invigorating the process. With Regards, Sami Salih. ________________________________ From: Ben Roberts - AfriNIC Sent: Thursday, October 9, 2025 12:58:24 am To: sami.salih at sustech.edu Cc: rpd at afrinic.net ; dc at darwincosta.com ; vincent at ngundi.me.ke ; Sami Salih Subject: Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual Sami, Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? Kind regards Ben Sent from my iPhone On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: ? Dear PDWG Community, I hope this message finds you well. I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: Previous PDWG Co-Chairs While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. AFRINIC Board We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. PDWG Community Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. With Regards. Sami Salih, PhD (ICT), PMP? Assistant Professor, Sudan University of Science and Technology Tel: (249) 122045707 _______________________________________________ Board mailing list -- board at afrinic.net To unsubscribe send an email to board-leave at afrinic.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From rashedibr at hotmail.com Thu Oct 9 06:40:16 2025 From: rashedibr at hotmail.com (Abdirashid Ibrahim Abdirahman) Date: Thu, 9 Oct 2025 06:40:16 +0000 Subject: [rpd] RPD Digest, Vol 214, Issue 9 In-Reply-To: References: Message-ID: Dear Sami Salih, AFRINIC Community Thank you for your thoughtful message and timely initiative. I fully support the resumption of the Policy Development Process and commend the renewed momentum following AFRINIC?s governance stabilization. Re-engaging the community and aligning our policies with global standards is indeed essential for strengthening AFRINIC?s role in Africa?s Internet ecosystem. Best regards, Abdirashid Ibrahim, Somaliland ________________________________ From: rpd-request at afrinic.net Sent: Wednesday, October 8, 2025 8:39 PM To: rpd at afrinic.net Subject: RPD Digest, Vol 214, Issue 9 Send RPD mailing list submissions to rpd at afrinic.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.afrinic.net/mailman/listinfo/rpd or, via email, send a message with subject or body 'help' to rpd-request at afrinic.net You can reach the person managing the list at rpd-owner at afrinic.net When replying, please edit your Subject line so it is more specific than "Re: Contents of RPD digest..." Today's Topics: 1. Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual (Sami Salih) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 Oct 2025 04:39:11 +0000 From: Sami Salih To: Ben Roberts - AfriNIC , "sami.salih at sustech.edu" Cc: "rpd at afrinic.net" Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual Message-ID: Content-Type: text/plain; charset="utf-8" Hi Ben We already have experts from all over the world actively proposing policies and debating both online and in meeting rooms. What we need now is simply for the Board to decide on the PDWG chairs to start engaging with the community in an official way. In parallel, organizing some online sessions to the community while preparing for the upcoming AFRINIC meeting would also greatly help in invigorating the process. With Regards, Sami Salih. ________________________________ From: Ben Roberts - AfriNIC Sent: Thursday, October 9, 2025 12:58:24 am To: sami.salih at sustech.edu Cc: rpd at afrinic.net ; dc at darwincosta.com ; vincent at ngundi.me.ke ; Sami Salih Subject: Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual Sami, Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? Kind regards Ben Sent from my iPhone On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: ? Dear PDWG Community, I hope this message finds you well. I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: Previous PDWG Co-Chairs While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. AFRINIC Board We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. PDWG Community Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. With Regards. Sami Salih, PhD (ICT), PMP? Assistant Professor, Sudan University of Science and Technology Tel: (249) 122045707 _______________________________________________ Board mailing list -- board at afrinic.net To unsubscribe send an email to board-leave at afrinic.net -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ------------------------------ End of RPD Digest, Vol 214, Issue 9 *********************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From dontommy24 at gmail.com Thu Oct 9 10:00:38 2025 From: dontommy24 at gmail.com (Tom Ochang) Date: Thu, 9 Oct 2025 11:00:38 +0100 Subject: [rpd] RPD Digest, Vol 214, Issue 9 In-Reply-To: References: Message-ID: Congratulations to the new AFRINIC board. It is cheering that the PDWG is spurring into life once more after the long hiatus. Obviously the break has left us with some policies that need review especially the WHOIS/PRIVACY policies which is my major area of interest, I will be glad to engage in discussions on the PDP on new policies whenever they are open for discussion. I wish the board all the best. Sincerely Yours, Ochang Thomas N. Chief Superintendent of Police. Nigeria Police Force. On Thu, Oct 9, 2025, 7:43 AM Abdirashid Ibrahim Abdirahman < rashedibr at hotmail.com> wrote: > *Dear Sami Salih, AFRINIC Community* > Thank you for your thoughtful message and timely initiative. I fully > support the resumption of the Policy Development Process and commend the > renewed momentum following AFRINIC?s governance stabilization. Re-engaging > the community and aligning our policies with global standards is indeed > essential for strengthening AFRINIC?s role in Africa?s Internet ecosystem. > Best regards, > *Abdirashid Ibrahim,* > *Somaliland* > > > ------------------------------ > *From:* rpd-request at afrinic.net > *Sent:* Wednesday, October 8, 2025 8:39 PM > *To:* rpd at afrinic.net > *Subject:* RPD Digest, Vol 214, Issue 9 > > Send RPD mailing list submissions to > rpd at afrinic.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.afrinic.net/mailman/listinfo/rpd > or, via email, send a message with subject or body 'help' to > rpd-request at afrinic.net > > You can reach the person managing the list at > rpd-owner at afrinic.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of RPD digest..." > > > Today's Topics: > > 1. Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC > Policy Manual (Sami Salih) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Oct 2025 04:39:11 +0000 > From: Sami Salih > To: Ben Roberts - AfriNIC , > "sami.salih at sustech.edu" > Cc: "rpd at afrinic.net" > Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the > AFRINIC Policy Manual > Message-ID: > < > GV1P194MB2421AA7D89F8989B7F4B91749BEEA at GV1P194MB2421.EURP194.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="utf-8" > > Hi Ben > > We already have experts from all over the world actively proposing > policies and debating both online and in meeting rooms. What we need now is > simply for the Board to decide on the PDWG chairs to start engaging with > the community in an official way. > > In parallel, organizing some online sessions to the community while > preparing for the upcoming AFRINIC meeting would also greatly help in > invigorating the process. > > With Regards, > Sami Salih. > > ________________________________ > From: Ben Roberts - AfriNIC > Sent: Thursday, October 9, 2025 12:58:24 am > To: sami.salih at sustech.edu > Cc: rpd at afrinic.net ; dc at darwincosta.com < > dc at darwincosta.com>; vincent at ngundi.me.ke ; Sami > Salih > Subject: Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC > Policy Manual > > Sami, > Thanks for your mail and we appreciate your contributions to PWDG to date > and are happy to see you are keen to start it up again. I am replying as a > community member, though I am also a board member of AfriNIC. > > I feel that as we restart the PWDG process, what is absolutely key is that > we get much more diversity in that process. My question back to you is to > ask, how do we invigorate the process to involve many more key experts in > the digital economy of Africa? > > Kind regards > Ben > > Sent from my iPhone > > On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: > > ? > Dear PDWG Community, > > I hope this message finds you well. > > I would like to take this opportunity to congratulate you all on the > successful election of the AFRINIC Board and the resumption of its proper > functioning. This milestone marks an important step toward restoring > stability, trust, and continuity in AFRINIC?s role as the Regional Internet > Registry for Africa. With governance now back on track, it is the right > moment to resume the Policy Development Process (PDP) and address the > policy gaps that have accumulated during the past three years of > interruption. > > As you are aware, over the past three years AFRINIC has gone through a > period of limited functionality, and the Policy Development Process (PDP) > has been effectively paused. During this time, the global Internet number > community has continued to evolve, with significant policy updates taking > place across the other RIRs. This has created a widening gap between > AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. > > In order to restore the momentum of policy development in our region and > to ensure that AFRINIC?s policy environment remains relevant, consistent, > and globally aligned, I would like to highlight the following areas where > action is needed: > > Previous PDWG Co-Chairs > While their terms have now ended, we request that the most recent PDWG > Co-Chairs prepare a short report summarizing the last set of policy > proposals that were under discussion before the process stalled. We further > encourage the original authors of those drafts to resubmit them for renewed > community review, or alternatively, invite any community member to take > initiative to re-submit and champion them. > > AFRINIC Board > We call on the Board to formally publish a community call for modernizing > the AFRINIC Policy Manual. This would include identifying and prioritizing > areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer > frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, > and membership/resource governance models). Such a call would help set a > clear direction and provide legitimacy to the process of catching up with > global best practices. > > PDWG Community > Most importantly, we urge all community members to actively re-engage in > the PDP by discussing any submitted proposals, providing constructive > feedback, and enriching the drafts with insights drawn from operational > experience. The strength of AFRINIC?s PDP has always been rooted in the > diversity and expertise of its community, and your participation will be > crucial in shaping the future of Internet number resource management in our > region. > > This is a collective responsibility, and now is the right moment to > re-energize our PDP and demonstrate the resilience of the AFRINIC community. > > With Regards. > > Sami Salih, PhD (ICT), PMP? > Assistant Professor, Sudan University of Science and Technology > Tel: (249) 122045707 > _______________________________________________ > Board mailing list -- board at afrinic.net > To unsubscribe send an email to board-leave at afrinic.net > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20251009/99f200cf/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > ------------------------------ > > End of RPD Digest, Vol 214, Issue 9 > *********************************** > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From guelordshadimiadi at gmail.com Thu Oct 9 10:45:14 2025 From: guelordshadimiadi at gmail.com (BINEMO SHADIMIADI Jean Guelord) Date: Thu, 9 Oct 2025 11:45:14 +0100 Subject: [rpd] RPD Digest, Vol 214, Issue 10 In-Reply-To: References: Message-ID: Je pris le temps de lire toute le proposition, Ce bien de relancer les activit?s d'?laboration de politique. Il faudra aussi renforcer la gouvernance et l'ind?pendance lors de discussion de ce politique pourque notre communaut? aie de politique durable et efficace. *BINEMO SHADIMIADI Jean GuelordCoordonnateur du Secr?tariat Provincial du Volontariat,Vice Pr?sident de la F?d?ration de la Promotion du Num?rique en Afrique, pr?sident du Centre de Convergence des Entrepreneurs du CongoCoach des PMes, Micro entreprise, EntreprenantsSp?cialiste en planification, entrepreneuriat, gestion des ressources humaines et fiscalit?;Formateur senior en initiative personnel, ?ducation financi?re, gestion des projets, cr?ation et gestion des entreprises et ONG;consultant en appuie conseil et entrepreneuriatguelordshadimiadi at gmail.com +243976451362+243816536891Whatsapp+243976451362Tweeter: https://twitter.com/jbinemo?lang=fr Facebook: https://www.facebook.com/jeanguelord.binemo LinkedIn:https://www.linkedin.com/in/jean-guelord-binemo-65bb72145 https://www.instagram.com/jeanguelord/ 88, Avenue Maniema, C/ Lubumbashi, Q/Kiwele, ville de Lubumbashi, Province du Haut Katanga* Le jeu. 9 oct. 2025, 11:02, a ?crit : > Send RPD mailing list submissions to > rpd at afrinic.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.afrinic.net/mailman/listinfo/rpd > or, via email, send a message with subject or body 'help' to > rpd-request at afrinic.net > > You can reach the person managing the list at > rpd-owner at afrinic.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of RPD digest..." > > > Today's Topics: > > 1. Re: RPD Digest, Vol 214, Issue 9 (Abdirashid Ibrahim Abdirahman) > 2. Re: RPD Digest, Vol 214, Issue 9 (Tom Ochang) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Oct 2025 06:40:16 +0000 > From: Abdirashid Ibrahim Abdirahman > To: "rpd at afrinic.net" , "sami.salih at outlook.com" > > Subject: Re: [rpd] RPD Digest, Vol 214, Issue 9 > Message-ID: > < > DM6PR19MB311325DC8538CF20F199D9DFBFEEA at DM6PR19MB3113.namprd19.prod.outlook.com > > > > Content-Type: text/plain; charset="windows-1252" > > Dear Sami Salih, AFRINIC Community > Thank you for your thoughtful message and timely initiative. I fully > support the resumption of the Policy Development Process and commend the > renewed momentum following AFRINIC?s governance stabilization. Re-engaging > the community and aligning our policies with global standards is indeed > essential for strengthening AFRINIC?s role in Africa?s Internet ecosystem. > Best regards, > Abdirashid Ibrahim, > Somaliland > > > ________________________________ > From: rpd-request at afrinic.net > Sent: Wednesday, October 8, 2025 8:39 PM > To: rpd at afrinic.net > Subject: RPD Digest, Vol 214, Issue 9 > > Send RPD mailing list submissions to > rpd at afrinic.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.afrinic.net/mailman/listinfo/rpd > or, via email, send a message with subject or body 'help' to > rpd-request at afrinic.net > > You can reach the person managing the list at > rpd-owner at afrinic.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of RPD digest..." > > > Today's Topics: > > 1. Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC > Policy Manual (Sami Salih) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Oct 2025 04:39:11 +0000 > From: Sami Salih > To: Ben Roberts - AfriNIC , > "sami.salih at sustech.edu" > Cc: "rpd at afrinic.net" > Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the > AFRINIC Policy Manual > Message-ID: > < > GV1P194MB2421AA7D89F8989B7F4B91749BEEA at GV1P194MB2421.EURP194.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="utf-8" > > Hi Ben > > We already have experts from all over the world actively proposing > policies and debating both online and in meeting rooms. What we need now is > simply for the Board to decide on the PDWG chairs to start engaging with > the community in an official way. > > In parallel, organizing some online sessions to the community while > preparing for the upcoming AFRINIC meeting would also greatly help in > invigorating the process. > > With Regards, > Sami Salih. > > ________________________________ > From: Ben Roberts - AfriNIC > Sent: Thursday, October 9, 2025 12:58:24 am > To: sami.salih at sustech.edu > Cc: rpd at afrinic.net ; dc at darwincosta.com < > dc at darwincosta.com>; vincent at ngundi.me.ke ; Sami > Salih > Subject: Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC > Policy Manual > > Sami, > Thanks for your mail and we appreciate your contributions to PWDG to date > and are happy to see you are keen to start it up again. I am replying as a > community member, though I am also a board member of AfriNIC. > > I feel that as we restart the PWDG process, what is absolutely key is that > we get much more diversity in that process. My question back to you is to > ask, how do we invigorate the process to involve many more key experts in > the digital economy of Africa? > > Kind regards > Ben > > Sent from my iPhone > > On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: > > ? > Dear PDWG Community, > > I hope this message finds you well. > > I would like to take this opportunity to congratulate you all on the > successful election of the AFRINIC Board and the resumption of its proper > functioning. This milestone marks an important step toward restoring > stability, trust, and continuity in AFRINIC?s role as the Regional Internet > Registry for Africa. With governance now back on track, it is the right > moment to resume the Policy Development Process (PDP) and address the > policy gaps that have accumulated during the past three years of > interruption. > > As you are aware, over the past three years AFRINIC has gone through a > period of limited functionality, and the Policy Development Process (PDP) > has been effectively paused. During this time, the global Internet number > community has continued to evolve, with significant policy updates taking > place across the other RIRs. This has created a widening gap between > AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. > > In order to restore the momentum of policy development in our region and > to ensure that AFRINIC?s policy environment remains relevant, consistent, > and globally aligned, I would like to highlight the following areas where > action is needed: > > Previous PDWG Co-Chairs > While their terms have now ended, we request that the most recent PDWG > Co-Chairs prepare a short report summarizing the last set of policy > proposals that were under discussion before the process stalled. We further > encourage the original authors of those drafts to resubmit them for renewed > community review, or alternatively, invite any community member to take > initiative to re-submit and champion them. > > AFRINIC Board > We call on the Board to formally publish a community call for modernizing > the AFRINIC Policy Manual. This would include identifying and prioritizing > areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer > frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, > and membership/resource governance models). Such a call would help set a > clear direction and provide legitimacy to the process of catching up with > global best practices. > > PDWG Community > Most importantly, we urge all community members to actively re-engage in > the PDP by discussing any submitted proposals, providing constructive > feedback, and enriching the drafts with insights drawn from operational > experience. The strength of AFRINIC?s PDP has always been rooted in the > diversity and expertise of its community, and your participation will be > crucial in shaping the future of Internet number resource management in our > region. > > This is a collective responsibility, and now is the right moment to > re-energize our PDP and demonstrate the resilience of the AFRINIC community. > > With Regards. > > Sami Salih, PhD (ICT), PMP? > Assistant Professor, Sudan University of Science and Technology > Tel: (249) 122045707 > _______________________________________________ > Board mailing list -- board at afrinic.net > To unsubscribe send an email to board-leave at afrinic.net > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20251009/99f200cf/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > ------------------------------ > > End of RPD Digest, Vol 214, Issue 9 > *********************************** > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20251009/128f115e/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Thu, 9 Oct 2025 11:00:38 +0100 > From: Tom Ochang > To: Abdirashid Ibrahim Abdirahman > Cc: AfriNIC Resource Policy Discussion List > Subject: Re: [rpd] RPD Digest, Vol 214, Issue 9 > Message-ID: > V2__4X+pz+FTbLW4A at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Congratulations to the new AFRINIC board. > It is cheering that the PDWG is spurring into life once more after the long > hiatus. Obviously the break has left us with some policies that need review > especially the WHOIS/PRIVACY policies which is my major area of interest, I > will be glad to engage in discussions on the PDP on new policies whenever > they are open for discussion. I wish the board all the best. > > Sincerely Yours, > Ochang Thomas N. > Chief Superintendent of Police. > Nigeria Police Force. > > > On Thu, Oct 9, 2025, 7:43 AM Abdirashid Ibrahim Abdirahman < > rashedibr at hotmail.com> wrote: > > > *Dear Sami Salih, AFRINIC Community* > > Thank you for your thoughtful message and timely initiative. I fully > > support the resumption of the Policy Development Process and commend the > > renewed momentum following AFRINIC?s governance stabilization. > Re-engaging > > the community and aligning our policies with global standards is indeed > > essential for strengthening AFRINIC?s role in Africa?s Internet > ecosystem. > > Best regards, > > *Abdirashid Ibrahim,* > > *Somaliland* > > > > > > ------------------------------ > > *From:* rpd-request at afrinic.net > > *Sent:* Wednesday, October 8, 2025 8:39 PM > > *To:* rpd at afrinic.net > > *Subject:* RPD Digest, Vol 214, Issue 9 > > > > Send RPD mailing list submissions to > > rpd at afrinic.net > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.afrinic.net/mailman/listinfo/rpd > > or, via email, send a message with subject or body 'help' to > > rpd-request at afrinic.net > > > > You can reach the person managing the list at > > rpd-owner at afrinic.net > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of RPD digest..." > > > > > > Today's Topics: > > > > 1. Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC > > Policy Manual (Sami Salih) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 9 Oct 2025 04:39:11 +0000 > > From: Sami Salih > > To: Ben Roberts - AfriNIC , > > "sami.salih at sustech.edu" > > Cc: "rpd at afrinic.net" > > Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the > > AFRINIC Policy Manual > > Message-ID: > > < > > > GV1P194MB2421AA7D89F8989B7F4B91749BEEA at GV1P194MB2421.EURP194.PROD.OUTLOOK.COM > > > > > > > Content-Type: text/plain; charset="utf-8" > > > > Hi Ben > > > > We already have experts from all over the world actively proposing > > policies and debating both online and in meeting rooms. What we need now > is > > simply for the Board to decide on the PDWG chairs to start engaging with > > the community in an official way. > > > > In parallel, organizing some online sessions to the community while > > preparing for the upcoming AFRINIC meeting would also greatly help in > > invigorating the process. > > > > With Regards, > > Sami Salih. > > > > ________________________________ > > From: Ben Roberts - AfriNIC > > Sent: Thursday, October 9, 2025 12:58:24 am > > To: sami.salih at sustech.edu > > Cc: rpd at afrinic.net ; dc at darwincosta.com < > > dc at darwincosta.com>; vincent at ngundi.me.ke ; Sami > > Salih > > Subject: Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC > > Policy Manual > > > > Sami, > > Thanks for your mail and we appreciate your contributions to PWDG to date > > and are happy to see you are keen to start it up again. I am replying as > a > > community member, though I am also a board member of AfriNIC. > > > > I feel that as we restart the PWDG process, what is absolutely key is > that > > we get much more diversity in that process. My question back to you is to > > ask, how do we invigorate the process to involve many more key experts in > > the digital economy of Africa? > > > > Kind regards > > Ben > > > > Sent from my iPhone > > > > On 6 Oct 2025, at 08:08, Sami Salih via Board wrote: > > > > ? > > Dear PDWG Community, > > > > I hope this message finds you well. > > > > I would like to take this opportunity to congratulate you all on the > > successful election of the AFRINIC Board and the resumption of its proper > > functioning. This milestone marks an important step toward restoring > > stability, trust, and continuity in AFRINIC?s role as the Regional > Internet > > Registry for Africa. With governance now back on track, it is the right > > moment to resume the Policy Development Process (PDP) and address the > > policy gaps that have accumulated during the past three years of > > interruption. > > > > As you are aware, over the past three years AFRINIC has gone through a > > period of limited functionality, and the Policy Development Process (PDP) > > has been effectively paused. During this time, the global Internet number > > community has continued to evolve, with significant policy updates taking > > place across the other RIRs. This has created a widening gap between > > AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. > > > > In order to restore the momentum of policy development in our region and > > to ensure that AFRINIC?s policy environment remains relevant, consistent, > > and globally aligned, I would like to highlight the following areas where > > action is needed: > > > > Previous PDWG Co-Chairs > > While their terms have now ended, we request that the most recent PDWG > > Co-Chairs prepare a short report summarizing the last set of policy > > proposals that were under discussion before the process stalled. We > further > > encourage the original authors of those drafts to resubmit them for > renewed > > community review, or alternatively, invite any community member to take > > initiative to re-submit and champion them. > > > > AFRINIC Board > > We call on the Board to formally publish a community call for modernizing > > the AFRINIC Policy Manual. This would include identifying and > prioritizing > > areas where policy alignment with other RIRs is needed (e.g., IPv4 > transfer > > frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy > reforms, > > and membership/resource governance models). Such a call would help set a > > clear direction and provide legitimacy to the process of catching up with > > global best practices. > > > > PDWG Community > > Most importantly, we urge all community members to actively re-engage in > > the PDP by discussing any submitted proposals, providing constructive > > feedback, and enriching the drafts with insights drawn from operational > > experience. The strength of AFRINIC?s PDP has always been rooted in the > > diversity and expertise of its community, and your participation will be > > crucial in shaping the future of Internet number resource management in > our > > region. > > > > This is a collective responsibility, and now is the right moment to > > re-energize our PDP and demonstrate the resilience of the AFRINIC > community. > > > > With Regards. > > > > Sami Salih, PhD (ICT), PMP? > > Assistant Professor, Sudan University of Science and Technology > > Tel: (249) 122045707 > > _______________________________________________ > > Board mailing list -- board at afrinic.net > > To unsubscribe send an email to board-leave at afrinic.net > > > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: < > > > https://lists.afrinic.net/pipermail/rpd/attachments/20251009/99f200cf/attachment.html > > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > RPD mailing list > > RPD at afrinic.net > > https://lists.afrinic.net/mailman/listinfo/rpd > > > > > > ------------------------------ > > > > End of RPD Digest, Vol 214, Issue 9 > > *********************************** > > _______________________________________________ > > RPD mailing list > > RPD at afrinic.net > > https://lists.afrinic.net/mailman/listinfo/rpd > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20251009/48a6742e/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > ------------------------------ > > End of RPD Digest, Vol 214, Issue 10 > ************************************ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Thu Oct 9 12:42:52 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Thu, 9 Oct 2025 14:42:52 +0200 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> Hi, That policy specifically may be one we may want to hold off until current membership status has been sorted out first.? Or at least the policy should be amended to compensate for what we've learned in the last five years. Kind regards, Jaco On 2025/10/09 02:21, Emmanuel Vitus wrote: > Good to see the list active again. Hopefully we can keep the energy > focused this time and not fall back into the long circular debates we > had in the past. > It could help to have a simple matrix showing which proposals can be > ratified quickly with little or no cost and which ones may need more > time or legal review. A timeline would also be useful to follow > progress taking into account the Board comments and the steps before > ratification. > The transfer policy should move forward as soon as possible,?my 2cents. > Cheers! > > - Emmanuel > > Le?jeu. 9 oct. 2025 ??00:18, jordi.palet--- via RPD > a ?crit?: > > Hi Caleb, > > The proposals that I refer: > 1) Already reached consensus. > 2) Already were sent to the board with the relevant reports. > > So from that perspective, with ?basically administrative? I mean > that there is not ?a lot of other? work to be done in the > proposals. Of course, the board should make sure that the > proposals aren?t against the company, but the legal implications, > operational feasibility, alignment with the bylaws, etc., was > already done because all this is part of the analysis impact that > was prepared *before* declaring consensus. This is just the way > the PDP works, so we aren?t changing anything. > > Saludos, > Jordi > > @jordipalet > > >> El 8 oct 2025, a las 18:07, Caleb Ogundele >> escribi?: >> >> Hi Jordi and All, >> >> I'm happy this list is?becoming more active, and it is a good thing. >> Responding to @Jordi, I must respectfully differ with Jordi on >> point one. While I share the desire to see pending proposals move >> forward, I don't believe board ratification should be >> characterized as "basically an administrative task that should >> not take too much time." >> >> Board ratification is a critical governance checkpoint where >> proposals are reviewed for legal implications, operational >> feasibility, and alignment with AFRINIC's mission and bylaws. >> Given that we're emerging from three years of limited >> functionality as?a community, I believe the Community and the >> Board deserve adequate time to properly review and ratify >> proposals, especially those that may have significant operational >> or financial implications for AFRINIC and its members. Times have >> changed in the last three years and community members have >> different views on certain policies. Rushing this process could >> lead to oversights that create problems down the line. Quality >> should take precedence over speed. >> >> *Caleb Ogundele* >> /Speaking for myself as a community member >> >> >> >> >> / >> >> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD >> wrote: >> >> HI Seun, all, >> >> Fully agree with your view. I will add 2 more points: >> >> 1) There are several policy proposals that reached consensus >> and are ?paused? just waiting for the board ratification. I >> understand the board will be very busy, but the ratification >> is basically an administrative task that should not take too >> much time. So please, consider doing so ASAP, so the >> implementation can also be initiated, as I think in some >> cases it may take long time. >> >> >> 2) Some of use may need to plan ahead, and buy our flights as >> early as possible (too close to the meeting become extremely >> expensive when traveling from abroad) for the next PPM, so it >> will be good to announce firm dates and location as soon as >> possible. >> >> Those that have policy proposals still under discussion >> really need to have a status summary and specially understand >> if the actual co-chairs will continue as suggested, so we can >> restart our work and encourage discussions in the community. >> >> Finally, I don?t think we need a ?complete modernization of >> the policy manual?, but instead concentrate in review the >> existing discussion and decide if we need to focus on any new >> topic at the time being. >> >> Tks! >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >>> El 8 oct 2025, a las 17:02, Seun Ojedeji >>> escribi?: >>> >>> Hello Ben, RPD >>> >>> It's good that this discussion is starting up. I don't think >>> anything revolutionary with the rpd needs to happen from the >>> board level at this time. The rpd itself should evolve >>> through policies and while the board indeed has the ability >>> to write a policy when required and in certain?circumstances >>> i do think that it isn't necessary at this time. I would >>> suggest the following: >>> >>> 1. Current Co-Chairs continue in their role towards the next >>> Public Policy Meeting (PPM) and they should coordinate on >>> the things Sami mentioned with regards to authors >>> representing their proposal and new proposals as applicable. >>> >>> 2. We usually hold 2 PPMs every year 1 during the AIS and >>> another at the second AFRINIC pubic meeting in the year, it >>> will be good for the Board to provide the rpd with some >>> information on how soon that can happen. >>> >>> 3. With the recent board election, staff does have >>> significant experience on conducting credible and verifiable >>> election. The Board should leverage on that to organise >>> election of Co-Chairs at the next ppm inline with the CPM. >>> The 2 seats should be filled in a staggered manner >>> >>> Regards >>> >>> ---- >>> Sent from my mobile >>> kindly excuse typos >>> >>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, >>> wrote: >>> >>> Sami, >>> Thanks for your mail and we appreciate your >>> contributions to PWDG to date and are happy to see you >>> are keen to start it up again. I am replying as a >>> community member, though I am also a board member of >>> AfriNIC. >>> >>> I feel that as we restart the PWDG process, what is >>> absolutely key is that we get *much more* diversity in >>> that process. My question back to you is to ask, how do >>> we invigorate the process to involve many more key >>> experts in the digital economy of Africa? >>> >>> Kind regards >>> Ben >>> >>> Sent from my iPhone >>> >>>> On 6 Oct 2025, at 08:08, Sami Salih via Board >>>> wrote: >>>> >>>> ? >>>> *Dear PDWG Community,* >>>> * >>>> * >>>> I hope this message finds you well. >>>> >>>> I would like to take this opportunity to congratulate >>>> you all on the successful election of the AFRINIC Board >>>> and the resumption of its proper functioning. This >>>> milestone marks an important step toward restoring >>>> stability, trust, and continuity in AFRINIC?s role as >>>> the Regional Internet Registry for Africa. With >>>> governance now back on track, it is the right moment to >>>> resume the Policy Development Process (PDP) and address >>>> the policy gaps that have accumulated during the past >>>> three years of interruption. >>>> >>>> As you are aware, over the past three years AFRINIC has >>>> gone through a period of limited functionality, and the >>>> Policy Development Process (PDP) has been effectively >>>> paused. During this time, the global Internet number >>>> community has continued to evolve, with significant >>>> policy updates taking place across the other RIRs. This >>>> has created a widening gap between AFRINIC?s >>>> Consolidated Policy Manual (CPM) and those of our >>>> sister RIRs. >>>> >>>> In order to restore the momentum of policy development >>>> in our region and to ensure that AFRINIC?s policy >>>> environment remains relevant, consistent, and globally >>>> aligned, I would like to highlight the following areas >>>> where action is needed: >>>> >>>> *Previous PDWG Co-Chairs* >>>> While their terms have now ended, we request that the >>>> most recent PDWG Co-Chairs prepare a short report >>>> summarizing the last set of policy proposals that were >>>> under discussion before the process stalled. We further >>>> encourage the original authors of those drafts to >>>> resubmit them for renewed community review, or >>>> alternatively, invite any community member to take >>>> initiative to re-submit and champion them. >>>> >>>> *AFRINIC Board* >>>> We call on the Board to formally publish a community >>>> call for modernizing the AFRINIC Policy Manual. This >>>> would include identifying and prioritizing areas where >>>> policy alignment with other RIRs is needed (e.g., IPv4 >>>> transfer frameworks, IPv6 allocation criteria, RPKI >>>> adoption, Whois/privacy reforms, and >>>> membership/resource governance models). Such a call >>>> would help set a clear direction and provide legitimacy >>>> to the process of catching up with global best practices. >>>> >>>> *PDWG Community* >>>> Most importantly, we urge all community members to >>>> actively re-engage in the PDP by discussing any >>>> submitted proposals, providing constructive feedback, >>>> and enriching the drafts with insights drawn from >>>> operational experience. The strength of AFRINIC?s PDP >>>> has always been rooted in the diversity and expertise >>>> of its community, and your participation will be >>>> crucial in shaping the future of Internet number >>>> resource management in our region. >>>> >>>> This is a collective responsibility, and now is the >>>> right moment to re-energize our PDP and demonstrate the >>>> resilience of the AFRINIC community. >>>> >>>> With Regards. >>>> >>>> *Sami Salih*, PhD (ICT), PMP? >>>> Assistant Professor, Sudan University of Science and >>>> Technology >>>> Tel: (249) 122045707 >>>> _______________________________________________ >>>> Board mailing list -- board at afrinic.net >>>> To unsubscribe send an email to board-leave at afrinic.net >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be >> privileged or confidential. The information is intended to be >> for the exclusive use of the individual(s) named above and >> further non-explicilty authorized disclosure, copying, >> distribution or use of the contents of this information, even >> if partially, including attached files, is strictly >> prohibited and will be considered a criminal offense. If you >> are not the intended recipient be aware that any disclosure, >> copying, distribution or use of the contents of this >> information, even if partially, including attached files, is >> strictly prohibited, will be considered a criminal offense, >> so you must reply to the original sender to inform about this >> communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> >> -- >> *Caleb Ogundele* >> Email: muyiwacaleb at gmail.com > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be > privileged or confidential. The information is intended to be for > the exclusive use of the individual(s) named above and further > non-explicilty authorized disclosure, copying, distribution or use > of the contents of this information, even if partially, including > attached files, is strictly prohibited and will be considered a > criminal offense. If you are not the intended recipient be aware > that any disclosure, copying, distribution or use of the contents > of this information, even if partially, including attached files, > is strictly prohibited, will be considered a criminal offense, so > you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Thu Oct 9 14:57:20 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Thu, 9 Oct 2025 08:57:20 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: <07C17A5A-B1CA-4D00-80F4-85A5F473D539@consulintel.es> Just to make sure about what I?m saying, I just re-read the bylaws and the PDP. In my opinion, the board can only ratify, nothing else. All the considerations have been already done during the PDP, including the impact analysis. Looking at the policies that are pending from ratification, I don?t think there is anything like a context change. In fact, several of the policies that reached consensus have also (and some of them with the same text), reached consensus and have been implemented meanwhile in other regions, which also shows that they are working well. The board change should not affect how they read the documents that were prepared during the PDP, otherwise, it will be very strange. Otherwise, we can have doubts of all the policy manual, because the new board could dislike something, not just the policies that already reached consensus. As said, I think the only reason the board could not ratify a policy is if it means creating damages to the company, which was not reported in any of the analysis impacts. Regards, Jordi @jordipalet > El 8 oct 2025, a las 18:48, Caleb Ogundele escribi?: > > Hi Jordi, > > Just a reminder that we have both been co-authors of a PDP process, which means you know I have an understanding of the PDP process, as you do. On the other hand, you're absolutely right that impact analysis is conducted before consensus is declared, and I appreciate you explaining that context at least to those who might be joining the PDP process recently. The board also has the right to send it back to the community for review. > > However, I still believe we should be cautious about characterizing board ratification as primarily administrative, even for proposals that reached consensus before the pause. Here's why: > > Context has changed significantly: These proposals reached consensus before the three-year interruption. The operational landscape, AFRINIC's financial position, staffing capabilities, and even other RIRs have evolved during this period. The Board has a fiduciary responsibility to reassess whether the original impact analyses still hold true given current circumstances. > > New Board composition: With the recent election, we have Board members who weren't part of the original discussions around these proposals. They need adequate time to review the proposals, understand the consensus process that led to them, and ask questions if needed. Expecting quick rubber-stamping doesn't serve good governance. > > Rebuilding trust requires thoroughness: After three years of limited functionality, the community needs to see that governance processes are working properly - not just quickly. A measured, transparent review by the Board (even if it takes a bit longer) will build more confidence than rushing through ratifications. > > Just to be clear, I absolutely agree that these proposals should move forward; however, technology has evolved in the last three years, and other RIRs have implemented new policies that may affect other issues. However, I share your concern about the timeline. > > Best regards, > > Caleb Ogundele > Speaking for myself as a community member > > > On Wed, Oct 8, 2025 at 7:24?PM jordi.palet--- via RPD > wrote: >> Hi Caleb, >> >> The proposals that I refer: >> 1) Already reached consensus. >> 2) Already were sent to the board with the relevant reports. >> >> So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >>> El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: >>> >>> Hi Jordi and All, >>> >>> I'm happy this list is becoming more active, and it is a good thing. >>> Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." >>> Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. >>> >>> Caleb Ogundele >>> Speaking for myself as a community member >>> >>> >>> >>> >>> >>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >>>> HI Seun, all, >>>> >>>> Fully agree with your view. I will add 2 more points: >>>> >>>> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >>>> >>> >>>> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >>>> >>>> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >>>> >>>> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >>>> >>>> Tks! >>>> >>>> Saludos, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>>>> >>>>> Hello Ben, RPD >>>>> >>>>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>>>> >>>>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>>>> >>>>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>>>> >>>>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>>>> >>>>> Regards >>>>> >>>>> ---- >>>>> Sent from my mobile >>>>> kindly excuse typos >>>>> >>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>>>>> Sami, >>>>>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>>>>> >>>>>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>>>>> >>>>>> Kind regards >>>>>> Ben >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>>>>> >>>>>>> ? >>>>>>> Dear PDWG Community, >>>>>>> >>>>>>> I hope this message finds you well. >>>>>>> >>>>>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>>>>> >>>>>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>>>> >>>>>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>>>>> >>>>>>> Previous PDWG Co-Chairs >>>>>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>>>>> >>>>>>> AFRINIC Board >>>>>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>>>>> >>>>>>> PDWG Community >>>>>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>>>>> >>>>>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>>>> >>>>>>> With Regards. >>>>>>> >>>>>>> Sami Salih, PhD (ICT), PMP? >>>>>>> Assistant Professor, Sudan University of Science and Technology >>>>>>> Tel: (249) 122045707 >>>>>>> _______________________________________________ >>>>>>> Board mailing list -- board at afrinic.net >>>>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> ********************************************** >>>> IPv4 is over >>>> Are you ready for the new Internet ? >>>> http://www.theipv6company.com >>>> The IPv6 Company >>>> >>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> >>> >>> -- >>> Caleb Ogundele >>> Email: muyiwacaleb at gmail.com >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > > > -- > Caleb Ogundele > Email: muyiwacaleb at gmail.com ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Thu Oct 9 15:02:16 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Thu, 9 Oct 2025 09:02:16 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: Yes Sami, you got it. However, also we must say that returning policies that reached consensus and had a positive impact analysis to the list will be like the board telling the authors and the rest of the community ?we don?t mind the time you had spend on this, we don?t trust you, you?re irrelevant because we are the board, etc.?, so I don?t think it is a good way to start if we want to trust the new board members. As I just said, the board can only ?not-ratify? a policy when it is going to harm the company. Hopefully they already followed the PDP discussions and they are able to be informed by the staff and read the reports that are prepared when a policy proposal reach consensus. Regards, Jordi @jordipalet > El 8 oct 2025, a las 22:29, Sami Salih escribi?: > > Thank you all for the active participation, I truly missed this spirit of debate. > > If I may echo and translate Jourdi?s point: we need the Board to either ratify the proposal or return it to the list. Keeping it pending for an unnecessary period is not helping anyone. > > In addition, we need the Board?s decision regarding the co-chair, as it is difficult to move forward without clear leadership and facilitation for the group. > > I?m very glad to see things getting back on track ? > > Best regards, > Sami > > Sent from Outlook for Android > From: Caleb Ogundele > Sent: Thursday, October 9, 2025 3:48:53 AM > To: jordi.palet at consulintel.es > Cc: rpd > Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual > > Hi Jordi, > > Just a reminder that we have both been co-authors of a PDP process, which means you know I have an understanding of the PDP process, as you do. On the other hand, you're absolutely right that impact analysis is conducted before consensus is declared, and I appreciate you explaining that context at least to those who might be joining the PDP process recently. The board also has the right to send it back to the community for review. > > However, I still believe we should be cautious about characterizing board ratification as primarily administrative, even for proposals that reached consensus before the pause. Here's why: > > Context has changed significantly: These proposals reached consensus before the three-year interruption. The operational landscape, AFRINIC's financial position, staffing capabilities, and even other RIRs have evolved during this period. The Board has a fiduciary responsibility to reassess whether the original impact analyses still hold true given current circumstances. > > New Board composition: With the recent election, we have Board members who weren't part of the original discussions around these proposals. They need adequate time to review the proposals, understand the consensus process that led to them, and ask questions if needed. Expecting quick rubber-stamping doesn't serve good governance. > > Rebuilding trust requires thoroughness: After three years of limited functionality, the community needs to see that governance processes are working properly - not just quickly. A measured, transparent review by the Board (even if it takes a bit longer) will build more confidence than rushing through ratifications. > > Just to be clear, I absolutely agree that these proposals should move forward; however, technology has evolved in the last three years, and other RIRs have implemented new policies that may affect other issues. However, I share your concern about the timeline. > > Best regards, > > Caleb Ogundele > Speaking for myself as a community member > > > On Wed, Oct 8, 2025 at 7:24?PM jordi.palet--- via RPD > wrote: > Hi Caleb, > > The proposals that I refer: > 1) Already reached consensus. > 2) Already were sent to the board with the relevant reports. > > So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. > > Saludos, > Jordi > > @jordipalet > > >> El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: >> >> Hi Jordi and All, >> >> I'm happy this list is becoming more active, and it is a good thing. >> Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." >> Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. >> >> Caleb Ogundele >> Speaking for myself as a community member >> >> >> >> >> >> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >> HI Seun, all, >> >> Fully agree with your view. I will add 2 more points: >> >> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >> >> >> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >> >> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >> >> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >> >> Tks! >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>> >>> Hello Ben, RPD >>> >>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>> >>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>> >>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>> >>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>> >>> Regards >>> >>> ---- >>> Sent from my mobile >>> kindly excuse typos >>> >>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>> Sami, >>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>> >>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>> >>> Kind regards >>> Ben >>> >>> Sent from my iPhone >>> >>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>> >>>> ? >>>> Dear PDWG Community, >>>> >>>> I hope this message finds you well. >>>> >>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>> >>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>> >>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>> >>>> Previous PDWG Co-Chairs >>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>> >>>> AFRINIC Board >>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>> >>>> PDWG Community >>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>> >>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>> >>>> With Regards. >>>> >>>> Sami Salih, PhD (ICT), PMP? >>>> Assistant Professor, Sudan University of Science and Technology >>>> Tel: (249) 122045707 >>>> _______________________________________________ >>>> Board mailing list -- board at afrinic.net >>>> To unsubscribe send an email to board-leave at afrinic.net >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> -- >> Caleb Ogundele >> Email: muyiwacaleb at gmail.com > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > -- > Caleb Ogundele > Email: muyiwacaleb at gmail.com ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Thu Oct 9 15:03:21 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Thu, 9 Oct 2025 09:03:21 -0600 Subject: [rpd] RPD Digest, Vol 214, Issue 9 In-Reply-To: References: Message-ID: <1FD7BA30-464E-481A-9AF5-B21C1ACF35B9@consulintel.es> I don?t recall there was any proposal related to changes in privacy that reached consensus? Regards, Jordi @jordipalet > El 9 oct 2025, a las 4:00, Tom Ochang escribi?: > > Congratulations to the new AFRINIC board. > It is cheering that the PDWG is spurring into life once more after the long hiatus. Obviously the break has left us with some policies that need review especially the WHOIS/PRIVACY policies which is my major area of interest, I will be glad to engage in discussions on the PDP on new policies whenever they are open for discussion. I wish the board all the best. > > Sincerely Yours, > Ochang Thomas N. > Chief Superintendent of Police. > Nigeria Police Force. > > > On Thu, Oct 9, 2025, 7:43 AM Abdirashid Ibrahim Abdirahman > wrote: >> Dear Sami Salih, AFRINIC Community >> Thank you for your thoughtful message and timely initiative. I fully support the resumption of the Policy Development Process and commend the renewed momentum following AFRINIC?s governance stabilization. Re-engaging the community and aligning our policies with global standards is indeed essential for strengthening AFRINIC?s role in Africa?s Internet ecosystem. >> Best regards, >> Abdirashid Ibrahim, >> Somaliland >> >> >> From: rpd-request at afrinic.net > >> Sent: Wednesday, October 8, 2025 8:39 PM >> To: rpd at afrinic.net > >> Subject: RPD Digest, Vol 214, Issue 9 >> >> Send RPD mailing list submissions to >> rpd at afrinic.net >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.afrinic.net/mailman/listinfo/rpd >> or, via email, send a message with subject or body 'help' to >> rpd-request at afrinic.net >> >> You can reach the person managing the list at >> rpd-owner at afrinic.net >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of RPD digest..." >> >> >> Today's Topics: >> >> 1. Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC >> Policy Manual (Sami Salih) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 9 Oct 2025 04:39:11 +0000 >> From: Sami Salih > >> To: Ben Roberts - AfriNIC >, >> "sami.salih at sustech.edu " > >> Cc: "rpd at afrinic.net " > >> Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the >> AFRINIC Policy Manual >> Message-ID: >> > >> >> Content-Type: text/plain; charset="utf-8" >> >> Hi Ben >> >> We already have experts from all over the world actively proposing policies and debating both online and in meeting rooms. What we need now is simply for the Board to decide on the PDWG chairs to start engaging with the community in an official way. >> >> In parallel, organizing some online sessions to the community while preparing for the upcoming AFRINIC meeting would also greatly help in invigorating the process. >> >> With Regards, >> Sami Salih. >> >> ________________________________ >> From: Ben Roberts - AfriNIC > >> Sent: Thursday, October 9, 2025 12:58:24 am >> To: sami.salih at sustech.edu > >> Cc: rpd at afrinic.net >; dc at darwincosta.com >; vincent at ngundi.me.ke >; Sami Salih > >> Subject: Re: [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual >> >> Sami, >> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >> >> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >> >> Kind regards >> Ben >> >> Sent from my iPhone >> >> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >> >> ? >> Dear PDWG Community, >> >> I hope this message finds you well. >> >> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >> >> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >> >> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >> >> Previous PDWG Co-Chairs >> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >> >> AFRINIC Board >> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >> >> PDWG Community >> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >> >> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >> >> With Regards. >> >> Sami Salih, PhD (ICT), PMP? >> Assistant Professor, Sudan University of Science and Technology >> Tel: (249) 122045707 >> _______________________________________________ >> Board mailing list -- board at afrinic.net >> To unsubscribe send an email to board-leave at afrinic.net >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ------------------------------ >> >> End of RPD Digest, Vol 214, Issue 9 >> *********************************** >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Thu Oct 9 15:10:50 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Thu, 9 Oct 2025 09:10:50 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> Message-ID: <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> I don?t think membership status has anything to do with PDP. Ideally PDP is contributed by many members actively participating, but I think this is not the case (not only in Afrinic, also in general in other RIRs). Even if I personally disagree with the transfer policy that got consensus declared, I think it should be ratified immediately, because implementation takes many months (as experienced by other RIRs). In that period, we still have the chance to improve it, if the community believe that needs to be done. Then small implementation changes can often be done very quickly. This is the same for any policy that reached consensus, even for the complete policy manual. It is a ?live law?, the community has the chance to*always* change or improve things. What it will be useless and long time consuming is when something that reached consensus (and had a positive impact analisys) is returned to the list to re-start again the full process. Again, if something can be improved, let?s do it based on the already approved text, not from scracth. Regards, Jordi @jordipalet > El 9 oct 2025, a las 6:42, Jaco Kroon escribi?: > > Hi, > > That policy specifically may be one we may want to hold off until current membership status has been sorted out first. Or at least the policy should be amended to compensate for what we've learned in the last five years. > > Kind regards, > Jaco > > On 2025/10/09 02:21, Emmanuel Vitus wrote: > >> Good to see the list active again. Hopefully we can keep the energy focused this time and not fall back into the long circular debates we had in the past. >> It could help to have a simple matrix showing which proposals can be ratified quickly with little or no cost and which ones may need more time or legal review. A timeline would also be useful to follow progress taking into account the Board comments and the steps before ratification. >> The transfer policy should move forward as soon as possible, my 2cents. >> Cheers! >> >> - Emmanuel >> >> Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD > a ?crit : >>> Hi Caleb, >>> >>> The proposals that I refer: >>> 1) Already reached consensus. >>> 2) Already were sent to the board with the relevant reports. >>> >>> So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. >>> >>> Saludos, >>> Jordi >>> >>> @jordipalet >>> >>> >>>> El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: >>>> >>>> Hi Jordi and All, >>>> >>>> I'm happy this list is becoming more active, and it is a good thing. >>>> Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." >>>> Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. >>>> >>>> Caleb Ogundele >>>> Speaking for myself as a community member >>>> >>>> >>>> >>>> >>>> >>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >>>>> HI Seun, all, >>>>> >>>>> Fully agree with your view. I will add 2 more points: >>>>> >>>>> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >>>>> >>>> >>>>> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >>>>> >>>>> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >>>>> >>>>> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >>>>> >>>>> Tks! >>>>> >>>>> Saludos, >>>>> Jordi >>>>> >>>>> @jordipalet >>>>> >>>>> >>>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>>>>> >>>>>> Hello Ben, RPD >>>>>> >>>>>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>>>>> >>>>>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>>>>> >>>>>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>>>>> >>>>>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>>>>> >>>>>> Regards >>>>>> >>>>>> ---- >>>>>> Sent from my mobile >>>>>> kindly excuse typos >>>>>> >>>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>>>>>> Sami, >>>>>>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>>>>>> >>>>>>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>>>>>> >>>>>>> Kind regards >>>>>>> Ben >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>>>>>> >>>>>>>> ? >>>>>>>> Dear PDWG Community, >>>>>>>> >>>>>>>> I hope this message finds you well. >>>>>>>> >>>>>>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>>>>>> >>>>>>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>>>>> >>>>>>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>>>>>> >>>>>>>> Previous PDWG Co-Chairs >>>>>>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>>>>>> >>>>>>>> AFRINIC Board >>>>>>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>>>>>> >>>>>>>> PDWG Community >>>>>>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>>>>>> >>>>>>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>>>>> >>>>>>>> With Regards. >>>>>>>> >>>>>>>> Sami Salih, PhD (ICT), PMP? >>>>>>>> Assistant Professor, Sudan University of Science and Technology >>>>>>>> Tel: (249) 122045707 >>>>>>>> _______________________________________________ >>>>>>>> Board mailing list -- board at afrinic.net >>>>>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> >>>>> ********************************************** >>>>> IPv4 is over >>>>> Are you ready for the new Internet ? >>>>> http://www.theipv6company.com >>>>> The IPv6 Company >>>>> >>>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> >>>> -- >>>> Caleb Ogundele >>>> Email: muyiwacaleb at gmail.com >>> >>> ********************************************** >>> IPv4 is over >>> Are you ready for the new Internet ? >>> http://www.theipv6company.com >>> The IPv6 Company >>> >>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dndannang at gmail.com Fri Oct 10 01:53:59 2025 From: dndannang at gmail.com (DANIEL NANGHAKA) Date: Fri, 10 Oct 2025 04:53:59 +0300 Subject: [rpd] Current Policy Proposals and Community Engagement in the PDP Message-ID: Dear Members, As part of our ongoing discussions within the Policy Development Process (PDP), I would like to draw your attention to the *current policy proposals* available on the AFRINIC website: ? https://afrinic.net/policy/proposals These proposals represent important steps in shaping Internet number resource management in our region, and your input is critical to ensure they reflect the needs and aspirations of our community. Caleb recently reminded us of a key point: *?Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC?s mission and bylaws. Given that we?re emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed.?* This perspective highlights the importance of a measured, inclusive, and well-informed deliberations as we restart the PDP process. In addition, Ben raised an equally important point on diversity and participation: *?I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa??* This is a challenge for all of us to consider. A more diverse and representative PDP will help ensure that the outcomes reflect the realities of Africa?s digital transformation and Internet growth. Some possible ways we might invigorate participation include: 1. *Targeted outreach* to universities, research networks, and ICT training institutions to bring in young technical experts and academics (this process is already ongoing with teh AFRINIC Fellowship Program). 2. *Engagement of the private sector* and tech industry leaders, particularly those driving Africa?s digital economy (startups, ISPs, fintechs, cloud providers, etc.). 3. *Partnerships with regional Internet and tech hubs* (AfriLabs, innovation hubs, NRENs, IXPs) to extend participation beyond the traditional AFRINIC community. 4. *Simplified communication and awareness tools* (short briefs, webinars, podcasts) to make policy discussions more accessible to non-specialists. 5. *Mentorship and capacity building* to help new voices actively contribute to proposal drafting and discussion (I was once a AFRINIC Fellow Mentor where I mentored over 10+ AFRINIC Fellows) I would like to invite community members to share their views on: 1. How we can practically improve participation and diversity in the PDP. 2. How we can ensure sufficient quality review and deliberation time, while maintaining momentum. Your contributions are essential to making the PDP stronger, more inclusive, and more effective. Best regards, Daniel Nanghaka Daniel Khauka. Chair - GovCom ICT & Digital Transformation Consultant | Knowledge Management & Innovation Specialist | Governance & Development Advisor Mobile +256 772 898298 (Uganda) ----------------------------------------- *"Working for Africa" * ----------------------------------------- ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Fri Oct 10 08:06:14 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Fri, 10 Oct 2025 10:06:14 +0200 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> Message-ID: <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Hi Jordi, I fully agree with what you say here. There are however pending disputes regarding legitimacy of a couple of members who could use the specific policy to sidestep the issue.? The policy needs to be adjusted to ensure that only members who's not only in good standing, but who is fully compliant with existing policies and where there are no ongoing disputes/court cases etc ... are allowed to transfer out. Kind regards, Jaco On 2025/10/09 17:10, jordi.palet--- via RPD wrote: > I don?t think membership status has anything to do with PDP. > > Ideally PDP is contributed by many members actively participating, but > I think this is not the case (not only in Afrinic, also in general in > other RIRs). > > Even if I personally disagree with the transfer policy that got > consensus declared, I think it should be ratified immediately, because > implementation takes many months (as experienced by other RIRs). In > that period, we still have the chance to improve it, if the community > believe that needs to be done. Then small implementation changes can > often be done very quickly. > > This is the same for any policy that reached consensus, even for the > complete policy manual. It is a ?live law?, the community has the > chance to*always* change or improve things. What it will be useless > and long time consuming is when something that reached consensus (and > had a positive impact analisys) is returned to the list to re-start > again the full process. Again, if something can be improved, let?s do > it based on the already approved text, not from scracth. > > Regards, > Jordi > > @jordipalet > > >> El 9 oct 2025, a las 6:42, Jaco Kroon escribi?: >> >> Hi, >> >> That policy specifically may be one we may want to hold off until >> current membership status has been sorted out first.? Or at least the >> policy should be amended to compensate for what we've learned in the >> last five years. >> >> Kind regards, >> Jaco >> >> On 2025/10/09 02:21, Emmanuel Vitus wrote: >> >>> Good to see the list active again. Hopefully we can keep the energy >>> focused this time and not fall back into the long circular debates >>> we had in the past. >>> It could help to have a simple matrix showing which proposals can be >>> ratified quickly with little or no cost and which ones may need more >>> time or legal review. A timeline would also be useful to follow >>> progress taking into account the Board comments and the steps before >>> ratification. >>> The transfer policy should move forward as soon as possible,?my 2cents. >>> Cheers! >>> >>> - Emmanuel >>> >>> Le?jeu. 9 oct. 2025 ??00:18, jordi.palet--- via RPD >>> a ?crit?: >>> >>> Hi Caleb, >>> >>> The proposals that I refer: >>> 1) Already reached consensus. >>> 2) Already were sent to the board with the relevant reports. >>> >>> So from that perspective, with ?basically administrative? I mean >>> that there is not ?a lot of other? work to be done in the >>> proposals. Of course, the board should make sure that the >>> proposals aren?t against the company, but the legal >>> implications, operational feasibility, alignment with the >>> bylaws, etc., was already done because all this is part of the >>> analysis impact that was prepared *before* declaring consensus. >>> This is just the way the PDP works, so we aren?t changing anything. >>> >>> Saludos, >>> Jordi >>> >>> @jordipalet >>> >>> >>>> El 8 oct 2025, a las 18:07, Caleb Ogundele >>>> escribi?: >>>> >>>> Hi Jordi and All, >>>> >>>> I'm happy this list is?becoming more active, and it is a good >>>> thing. >>>> Responding to @Jordi, I must respectfully differ with Jordi on >>>> point one. While I share the desire to see pending proposals >>>> move forward, I don't believe board ratification should be >>>> characterized as "basically an administrative task that should >>>> not take too much time." >>>> >>>> Board ratification is a critical governance checkpoint where >>>> proposals are reviewed for legal implications, operational >>>> feasibility, and alignment with AFRINIC's mission and bylaws. >>>> Given that we're emerging from three years of limited >>>> functionality as?a community, I believe the Community and the >>>> Board deserve adequate time to properly review and ratify >>>> proposals, especially those that may have significant >>>> operational or financial implications for AFRINIC and its >>>> members. Times have changed in the last three years and >>>> community members have different views on certain policies. >>>> Rushing this process could lead to oversights that create >>>> problems down the line. Quality should take precedence over speed. >>>> >>>> *Caleb Ogundele* >>>> /Speaking for myself as a community member >>>> >>>> >>>> >>>> >>>> / >>>> >>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD >>>> wrote: >>>> >>>> HI Seun, all, >>>> >>>> Fully agree with your view. I will add 2 more points: >>>> >>>> 1) There are several policy proposals that reached >>>> consensus and are ?paused? just waiting for the board >>>> ratification. I understand the board will be very busy, but >>>> the ratification is basically an administrative task that >>>> should not take too much time. So please, consider doing so >>>> ASAP, so the implementation can also be initiated, as I >>>> think in some cases it may take long time. >>>> >>>> >>>> 2) Some of use may need to plan ahead, and buy our flights >>>> as early as possible (too close to the meeting become >>>> extremely expensive when traveling from abroad) for the >>>> next PPM, so it will be good to announce firm dates and >>>> location as soon as possible. >>>> >>>> Those that have policy proposals still under discussion >>>> really need to have a status summary and specially >>>> understand if the actual co-chairs will continue as >>>> suggested, so we can restart our work and encourage >>>> discussions in the community. >>>> >>>> Finally, I don?t think we need a ?complete modernization of >>>> the policy manual?, but instead concentrate in review the >>>> existing discussion and decide if we need to focus on any >>>> new topic at the time being. >>>> >>>> Tks! >>>> >>>> Saludos, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji >>>>> escribi?: >>>>> >>>>> Hello Ben, RPD >>>>> >>>>> It's good that this discussion is starting up. I don't >>>>> think anything revolutionary with the rpd needs to happen >>>>> from the board level at this time. The rpd itself should >>>>> evolve through policies and while the board indeed has the >>>>> ability to write a policy when required and in >>>>> certain?circumstances i do think that it isn't necessary >>>>> at this time. I would suggest the following: >>>>> >>>>> 1. Current Co-Chairs continue in their role towards the >>>>> next Public Policy Meeting (PPM) and they should >>>>> coordinate on the things Sami mentioned with regards to >>>>> authors representing their proposal and new proposals as >>>>> applicable. >>>>> >>>>> 2. We usually hold 2 PPMs every year 1 during the AIS and >>>>> another at the second AFRINIC pubic meeting in the year, >>>>> it will be good for the Board to provide the rpd with some >>>>> information on how soon that can happen. >>>>> >>>>> 3. With the recent board election, staff does have >>>>> significant experience on conducting credible and >>>>> verifiable election. The Board should leverage on that to >>>>> organise election of Co-Chairs at the next ppm inline with >>>>> the CPM. The 2 seats should be filled in a staggered manner >>>>> >>>>> Regards >>>>> >>>>> ---- >>>>> Sent from my mobile >>>>> kindly excuse typos >>>>> >>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, >>>>> wrote: >>>>> >>>>> Sami, >>>>> Thanks for your mail and we appreciate your >>>>> contributions to PWDG to date and are happy to see you >>>>> are keen to start it up again. I am replying as a >>>>> community member, though I am also a board member of >>>>> AfriNIC. >>>>> >>>>> I feel that as we restart the PWDG process, what is >>>>> absolutely key is that we get *much more* diversity in >>>>> that process. My question back to you is to ask, how >>>>> do we invigorate the process to involve many more key >>>>> experts in the digital economy of Africa? >>>>> >>>>> Kind regards >>>>> Ben >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board >>>>>> wrote: >>>>>> >>>>>> ? >>>>>> *Dear PDWG Community,* >>>>>> * >>>>>> * >>>>>> I hope this message finds you well. >>>>>> >>>>>> I would like to take this opportunity to congratulate >>>>>> you all on the successful election of the AFRINIC >>>>>> Board and the resumption of its proper functioning. >>>>>> This milestone marks an important step toward >>>>>> restoring stability, trust, and continuity in >>>>>> AFRINIC?s role as the Regional Internet Registry for >>>>>> Africa. With governance now back on track, it is the >>>>>> right moment to resume the Policy Development Process >>>>>> (PDP) and address the policy gaps that have >>>>>> accumulated during the past three years of interruption. >>>>>> >>>>>> As you are aware, over the past three years AFRINIC >>>>>> has gone through a period of limited functionality, >>>>>> and the Policy Development Process (PDP) has been >>>>>> effectively paused. During this time, the global >>>>>> Internet number community has continued to evolve, >>>>>> with significant policy updates taking place across >>>>>> the other RIRs. This has created a widening gap >>>>>> between AFRINIC?s Consolidated Policy Manual (CPM) >>>>>> and those of our sister RIRs. >>>>>> >>>>>> In order to restore the momentum of policy >>>>>> development in our region and to ensure that >>>>>> AFRINIC?s policy environment remains relevant, >>>>>> consistent, and globally aligned, I would like to >>>>>> highlight the following areas where action is needed: >>>>>> >>>>>> *Previous PDWG Co-Chairs* >>>>>> While their terms have now ended, we request that the >>>>>> most recent PDWG Co-Chairs prepare a short report >>>>>> summarizing the last set of policy proposals that >>>>>> were under discussion before the process stalled. We >>>>>> further encourage the original authors of those >>>>>> drafts to resubmit them for renewed community review, >>>>>> or alternatively, invite any community member to take >>>>>> initiative to re-submit and champion them. >>>>>> >>>>>> *AFRINIC Board* >>>>>> We call on the Board to formally publish a community >>>>>> call for modernizing the AFRINIC Policy Manual. This >>>>>> would include identifying and prioritizing areas >>>>>> where policy alignment with other RIRs is needed >>>>>> (e.g., IPv4 transfer frameworks, IPv6 allocation >>>>>> criteria, RPKI adoption, Whois/privacy reforms, and >>>>>> membership/resource governance models). Such a call >>>>>> would help set a clear direction and provide >>>>>> legitimacy to the process of catching up with global >>>>>> best practices. >>>>>> >>>>>> *PDWG Community* >>>>>> Most importantly, we urge all community members to >>>>>> actively re-engage in the PDP by discussing any >>>>>> submitted proposals, providing constructive feedback, >>>>>> and enriching the drafts with insights drawn from >>>>>> operational experience. The strength of AFRINIC?s PDP >>>>>> has always been rooted in the diversity and expertise >>>>>> of its community, and your participation will be >>>>>> crucial in shaping the future of Internet number >>>>>> resource management in our region. >>>>>> >>>>>> This is a collective responsibility, and now is the >>>>>> right moment to re-energize our PDP and demonstrate >>>>>> the resilience of the AFRINIC community. >>>>>> >>>>>> With Regards. >>>>>> >>>>>> *Sami Salih*, PhD (ICT), PMP? >>>>>> Assistant Professor, Sudan University of Science and >>>>>> Technology >>>>>> Tel: (249) 122045707 >>>>>> _______________________________________________ >>>>>> Board mailing list -- board at afrinic.net >>>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> ********************************************** >>>> IPv4 is over >>>> Are you ready for the new Internet ? >>>> http://www.theipv6company.com >>>> The IPv6 Company >>>> >>>> This electronic message contains information which may be >>>> privileged or confidential. The information is intended to >>>> be for the exclusive use of the individual(s) named above >>>> and further non-explicilty authorized disclosure, copying, >>>> distribution or use of the contents of this information, >>>> even if partially, including attached files, is strictly >>>> prohibited and will be considered a criminal offense. If >>>> you are not the intended recipient be aware that any >>>> disclosure, copying, distribution or use of the contents of >>>> this information, even if partially, including attached >>>> files, is strictly prohibited, will be considered a >>>> criminal offense, so you must reply to the original sender >>>> to inform about this communication and delete it. >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> >>>> -- >>>> *Caleb Ogundele* >>>> Email: muyiwacaleb at gmail.com >>> >>> >>> ********************************************** >>> IPv4 is over >>> Are you ready for the new Internet ? >>> http://www.theipv6company.com >>> The IPv6 Company >>> >>> This electronic message contains information which may be >>> privileged or confidential. The information is intended to be >>> for the exclusive use of the individual(s) named above and >>> further non-explicilty authorized disclosure, copying, >>> distribution or use of the contents of this information, even if >>> partially, including attached files, is strictly prohibited and >>> will be considered a criminal offense. If you are not the >>> intended recipient be aware that any disclosure, copying, >>> distribution or use of the contents of this information, even if >>> partially, including attached files, is strictly prohibited, >>> will be considered a criminal offense, so you must reply to the >>> original sender to inform about this communication and delete it. >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged > or confidential. The information is intended to be for the exclusive > use of the individual(s) named above and further non-explicilty > authorized disclosure, copying, distribution or use of the contents of > this information, even if partially, including attached files, is > strictly prohibited and will be considered a criminal offense. If you > are not the intended recipient be aware that any disclosure, copying, > distribution or use of the contents of this information, even if > partially, including attached files, is strictly prohibited, will be > considered a criminal offense, so you must reply to the original > sender to inform about this communication and delete it. > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From mamattah.raymond at gmail.com Fri Oct 10 08:43:07 2025 From: mamattah.raymond at gmail.com (Raymond Mamattah) Date: Fri, 10 Oct 2025 08:43:07 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: Great discussions! My one cent is that due to the impasse we have had, which is due partly to AFRINIC's own by-laws/policies, I think the Board would have to look critically and with multiple checks before ratifying any policy. I also think we should not push for a policy that's not already passed to be hurriedly ratified. Ideally such policies should go through "public comments" for critical checks before being passed on for ratification. Care must be taken so we don't have a "stone-around our neck to make us easily sink" again. Regards, --- Raymond Mamattah Accra, Ghana ?? On Fri, 10 Oct 2025, 08:10 Jaco Kroon, wrote: > Hi Jordi, > > I fully agree with what you say here. > > There are however pending disputes regarding legitimacy of a couple of > members who could use the specific policy to sidestep the issue. The > policy needs to be adjusted to ensure that only members who's not only in > good standing, but who is fully compliant with existing policies and where > there are no ongoing disputes/court cases etc ... are allowed to transfer > out. > > Kind regards, > Jaco > On 2025/10/09 17:10, jordi.palet--- via RPD wrote: > > I don?t think membership status has anything to do with PDP. > > Ideally PDP is contributed by many members actively participating, but I > think this is not the case (not only in Afrinic, also in general in other > RIRs). > > Even if I personally disagree with the transfer policy that got consensus > declared, I think it should be ratified immediately, because implementation > takes many months (as experienced by other RIRs). In that period, we still > have the chance to improve it, if the community believe that needs to be > done. Then small implementation changes can often be done very quickly. > > This is the same for any policy that reached consensus, even for the > complete policy manual. It is a ?live law?, the community has the chance > to*always* change or improve things. What it will be useless and long time > consuming is when something that reached consensus (and had a positive > impact analisys) is returned to the list to re-start again the full > process. Again, if something can be improved, let?s do it based on the > already approved text, not from scracth. > > Regards, > Jordi > > @jordipalet > > > El 9 oct 2025, a las 6:42, Jaco Kroon > escribi?: > > Hi, > > That policy specifically may be one we may want to hold off until current > membership status has been sorted out first. Or at least the policy should > be amended to compensate for what we've learned in the last five years. > > Kind regards, > Jaco > > On 2025/10/09 02:21, Emmanuel Vitus wrote: > > Good to see the list active again. Hopefully we can keep the energy > focused this time and not fall back into the long circular debates we had > in the past. > It could help to have a simple matrix showing which proposals can be > ratified quickly with little or no cost and which ones may need more time > or legal review. A timeline would also be useful to follow progress taking > into account the Board comments and the steps before ratification. > The transfer policy should move forward as soon as possible, my 2cents. > Cheers! > > - Emmanuel > > Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD a > ?crit : > >> Hi Caleb, >> >> The proposals that I refer: >> 1) Already reached consensus. >> 2) Already were sent to the board with the relevant reports. >> >> So from that perspective, with ?basically administrative? I mean that >> there is not ?a lot of other? work to be done in the proposals. Of course, >> the board should make sure that the proposals aren?t against the company, >> but the legal implications, operational feasibility, alignment with the >> bylaws, etc., was already done because all this is part of the analysis >> impact that was prepared *before* declaring consensus. This is just the way >> the PDP works, so we aren?t changing anything. >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >> El 8 oct 2025, a las 18:07, Caleb Ogundele >> escribi?: >> >> Hi Jordi and All, >> >> I'm happy this list is becoming more active, and it is a good thing. >> Responding to @Jordi, I must respectfully differ with Jordi on point one. >> While I share the desire to see pending proposals move forward, I don't >> believe board ratification should be characterized as "basically an >> administrative task that should not take too much time." >> >> Board ratification is a critical governance checkpoint where proposals >> are reviewed for legal implications, operational feasibility, and alignment >> with AFRINIC's mission and bylaws. Given that we're emerging from three >> years of limited functionality as a community, I believe the Community and >> the Board deserve adequate time to properly review and ratify proposals, >> especially those that may have significant operational or financial >> implications for AFRINIC and its members. Times have changed in the last >> three years and community members have different views on certain policies. >> Rushing this process could lead to oversights that create problems down the >> line. Quality should take precedence over speed. >> *Caleb Ogundele* >> >> >> >> >> >> *Speaking for myself as a community member * >> >> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD >> wrote: >> >>> HI Seun, all, >>> >>> Fully agree with your view. I will add 2 more points: >>> >>> 1) There are several policy proposals that reached consensus and are >>> ?paused? just waiting for the board ratification. I understand the board >>> will be very busy, but the ratification is basically an administrative task >>> that should not take too much time. So please, consider doing so ASAP, so >>> the implementation can also be initiated, as I think in some cases it may >>> take long time. >>> >>> >> 2) Some of use may need to plan ahead, and buy our flights as early as >>> possible (too close to the meeting become extremely expensive when >>> traveling from abroad) for the next PPM, so it will be good to announce >>> firm dates and location as soon as possible. >>> >>> Those that have policy proposals still under discussion really need to >>> have a status summary and specially understand if the actual co-chairs will >>> continue as suggested, so we can restart our work and encourage discussions >>> in the community. >>> >>> Finally, I don?t think we need a ?complete modernization of the policy >>> manual?, but instead concentrate in review the existing discussion and >>> decide if we need to focus on any new topic at the time being. >>> >>> Tks! >>> >>> Saludos, >>> Jordi >>> >>> @jordipalet >>> >>> >>> El 8 oct 2025, a las 17:02, Seun Ojedeji >>> escribi?: >>> >>> Hello Ben, RPD >>> >>> It's good that this discussion is starting up. I don't think anything >>> revolutionary with the rpd needs to happen from the board level at this >>> time. The rpd itself should evolve through policies and while the board >>> indeed has the ability to write a policy when required and in >>> certain circumstances i do think that it isn't necessary at this time. I >>> would suggest the following: >>> >>> 1. Current Co-Chairs continue in their role towards the next Public >>> Policy Meeting (PPM) and they should coordinate on the things Sami >>> mentioned with regards to authors representing their proposal and new >>> proposals as applicable. >>> >>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the >>> second AFRINIC pubic meeting in the year, it will be good for the Board to >>> provide the rpd with some information on how soon that can happen. >>> >>> 3. With the recent board election, staff does have significant >>> experience on conducting credible and verifiable election. The Board should >>> leverage on that to organise election of Co-Chairs at the next ppm inline >>> with the CPM. The 2 seats should be filled in a staggered manner >>> >>> Regards >>> >>> ---- >>> Sent from my mobile >>> kindly excuse typos >>> >>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, < >>> rpd at afrinic.net> wrote: >>> >>>> Sami, >>>> Thanks for your mail and we appreciate your contributions to PWDG to >>>> date and are happy to see you are keen to start it up again. I am replying >>>> as a community member, though I am also a board member of AfriNIC. >>>> >>>> I feel that as we restart the PWDG process, what is absolutely key is >>>> that we get *much more* diversity in that process. My question back to >>>> you is to ask, how do we invigorate the process to involve many more key >>>> experts in the digital economy of Africa? >>>> >>>> Kind regards >>>> Ben >>>> >>>> Sent from my iPhone >>>> >>>> On 6 Oct 2025, at 08:08, Sami Salih via Board >>>> wrote: >>>> >>>> ? >>>> *Dear PDWG Community,* >>>> >>>> I hope this message finds you well. >>>> >>>> I would like to take this opportunity to congratulate you all on the >>>> successful election of the AFRINIC Board and the resumption of its proper >>>> functioning. This milestone marks an important step toward restoring >>>> stability, trust, and continuity in AFRINIC?s role as the Regional Internet >>>> Registry for Africa. With governance now back on track, it is the right >>>> moment to resume the Policy Development Process (PDP) and address the >>>> policy gaps that have accumulated during the past three years of >>>> interruption. >>>> >>>> As you are aware, over the past three years AFRINIC has gone through a >>>> period of limited functionality, and the Policy Development Process (PDP) >>>> has been effectively paused. During this time, the global Internet number >>>> community has continued to evolve, with significant policy updates taking >>>> place across the other RIRs. This has created a widening gap between >>>> AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>> >>>> In order to restore the momentum of policy development in our region >>>> and to ensure that AFRINIC?s policy environment remains relevant, >>>> consistent, and globally aligned, I would like to highlight the following >>>> areas where action is needed: >>>> >>>> *Previous PDWG Co-Chairs* >>>> While their terms have now ended, we request that the most recent PDWG >>>> Co-Chairs prepare a short report summarizing the last set of policy >>>> proposals that were under discussion before the process stalled. We further >>>> encourage the original authors of those drafts to resubmit them for renewed >>>> community review, or alternatively, invite any community member to take >>>> initiative to re-submit and champion them. >>>> >>>> *AFRINIC Board* >>>> We call on the Board to formally publish a community call for >>>> modernizing the AFRINIC Policy Manual. This would include identifying and >>>> prioritizing areas where policy alignment with other RIRs is needed (e.g., >>>> IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, >>>> Whois/privacy reforms, and membership/resource governance models). Such a >>>> call would help set a clear direction and provide legitimacy to the process >>>> of catching up with global best practices. >>>> >>>> *PDWG Community* >>>> Most importantly, we urge all community members to actively re-engage >>>> in the PDP by discussing any submitted proposals, providing constructive >>>> feedback, and enriching the drafts with insights drawn from operational >>>> experience. The strength of AFRINIC?s PDP has always been rooted in the >>>> diversity and expertise of its community, and your participation will be >>>> crucial in shaping the future of Internet number resource management in our >>>> region. >>>> >>>> This is a collective responsibility, and now is the right moment to >>>> re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>> >>>> With Regards. >>>> >>>> *Sami Salih*, PhD (ICT), PMP? >>>> Assistant Professor, Sudan University of Science and Technology >>>> Tel: (249) 122045707 >>>> _______________________________________________ >>>> Board mailing list -- board at afrinic.net >>>> To unsubscribe send an email to board-leave at afrinic.net >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> >>> >>> ********************************************** >>> IPv4 is over >>> Are you ready for the new Internet ? >>> http://www.theipv6company.com >>> The IPv6 Company >>> >>> This electronic message contains information which may be privileged or >>> confidential. The information is intended to be for the exclusive use of >>> the individual(s) named above and further non-explicilty authorized >>> disclosure, copying, distribution or use of the contents of this >>> information, even if partially, including attached files, is strictly >>> prohibited and will be considered a criminal offense. If you are not the >>> intended recipient be aware that any disclosure, copying, distribution or >>> use of the contents of this information, even if partially, including >>> attached files, is strictly prohibited, will be considered a criminal >>> offense, so you must reply to the original sender to inform about this >>> communication and delete it. >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> >> >> -- >> *Caleb Ogundele* >> Email: muyiwacaleb at gmail.com >> >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or >> confidential. The information is intended to be for the exclusive use of >> the individual(s) named above and further non-explicilty authorized >> disclosure, copying, distribution or use of the contents of this >> information, even if partially, including attached files, is strictly >> prohibited and will be considered a criminal offense. If you are not the >> intended recipient be aware that any disclosure, copying, distribution or >> use of the contents of this information, even if partially, including >> attached files, is strictly prohibited, will be considered a criminal >> offense, so you must reply to the original sender to inform about this >> communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > > _______________________________________________ > RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > > _______________________________________________ > RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Fri Oct 10 09:12:04 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Fri, 10 Oct 2025 11:12:04 +0200 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: Hi Raymond, Jordi is right in that once policies have been passed to the board it's not really trivial for them to push it back to the PDP, and Jordi is also right in that "what gives them the right?" (which is what I paraphrased from his writing).? That's a very valid question. I would personally rather have the board be on the side of caution, and send everything back to the chairs to revalidate, as new inputs from the last couple of years may very well result in a different impact assessment. I do also think that going forward we need to have a legal assessment on all new policies too - even if (in my made up estimation) the far bulk of policies will not have legal implications, however, contracts may be impacted by policies. Specifically, some of the sticky points that came up in discussion: 1.? Can rule/policy changes be enforced retroactively? 2.? If a contract specifically states you're allowed to do xyz, does that preclude everything else, or is only what is specifically precluded contractually precluded? To make this even more sticky, let's say that a new policy takes away a right you previously had (implied or otherwise, for example, the topic of whether you're allowed to lease/sell/broker Afrinic IPv4 space, which is hotly debated with some saying you're allowed to and some saying you're not - I have my opinions on this but that's orthogonal to discussion I'm trying to have so please treat it as an example and not the topic), is that enforceable? What if a new policy/rule gives you a new right you didn't have previously? Clearly there are potentially legal implications here that can (and plainly has) negatively impacted the company (Afrinic).? And hopefully it's clear that the answers are not clear cut black and white, even though we'd like them to be. I think given the above a pause is in order to allow a re-assessment of all policies that has been submitted to board for ratification. I would also like to know if there is a list of such policies, and where it can be found, or if one of the staff members are possibly in a position to provide such a list, along with the wording impact on the CPM and the impact assessments that were provided. This should allow the PDWG to quickly state "we're OK with these proceeding, we'd like these back" etc ... assuming no one points out a policy issue with what I'm proposing. Kind regards, Jaco On 2025/10/10 10:43, Raymond Mamattah wrote: > Great discussions! > > My one cent is that due to the impasse we have had, which is due > partly to AFRINIC's own by-laws/policies, I think the Board would have > to look critically and with multiple checks before ratifying any policy. > > I also think we should not push for a policy that's not already passed > to be hurriedly ratified. Ideally such policies should go through > "public comments" for critical checks before being passed on for > ratification. > > Care must be taken so we don't have a "stone-around our neck to make > us easily sink" again. > > Regards, > > --- > Raymond Mamattah > Accra, Ghana ?? > > On Fri, 10 Oct 2025, 08:10 Jaco Kroon, wrote: > > Hi Jordi, > > I fully agree with what you say here. > > There are however pending disputes regarding legitimacy of a > couple of members who could use the specific policy to sidestep > the issue.? The policy needs to be adjusted to ensure that only > members who's not only in good standing, but who is fully > compliant with existing policies and where there are no ongoing > disputes/court cases etc ... are allowed to transfer out. > > Kind regards, > Jaco > > On 2025/10/09 17:10, jordi.palet--- via RPD wrote: >> I don?t think membership status has anything to do with PDP. >> >> Ideally PDP is contributed by many members actively >> participating, but I think this is not the case (not only in >> Afrinic, also in general in other RIRs). >> >> Even if I personally disagree with the transfer policy that got >> consensus declared, I think it should be ratified immediately, >> because implementation takes many months (as experienced by other >> RIRs). In that period, we still have the chance to improve it, if >> the community believe that needs to be done. Then small >> implementation changes can often be done very quickly. >> >> This is the same for any policy that reached consensus, even for >> the complete policy manual. It is a ?live law?, the community has >> the chance to*always* change or improve things. What it will be >> useless and long time consuming is when something that reached >> consensus (and had a positive impact analisys) is returned to the >> list to re-start again the full process. Again, if something can >> be improved, let?s do it based on the already approved text, not >> from scracth. >> >> Regards, >> Jordi >> >> @jordipalet >> >> >>> El 9 oct 2025, a las 6:42, Jaco Kroon >>> escribi?: >>> >>> Hi, >>> >>> That policy specifically may be one we may want to hold off >>> until current membership status has been sorted out first.? Or >>> at least the policy should be amended to compensate for what >>> we've learned in the last five years. >>> >>> Kind regards, >>> Jaco >>> >>> On 2025/10/09 02:21, Emmanuel Vitus wrote: >>> >>>> Good to see the list active again. Hopefully we can keep the >>>> energy focused this time and not fall back into the long >>>> circular debates we had in the past. >>>> It could help to have a simple matrix showing which proposals >>>> can be ratified quickly with little or no cost and which ones >>>> may need more time or legal review. A timeline would also be >>>> useful to follow progress taking into account the Board >>>> comments and the steps before ratification. >>>> The transfer policy should move forward as soon as possible,?my >>>> 2cents. >>>> Cheers! >>>> >>>> - Emmanuel >>>> >>>> Le?jeu. 9 oct. 2025 ??00:18, jordi.palet--- via RPD >>>> a ?crit?: >>>> >>>> Hi Caleb, >>>> >>>> The proposals that I refer: >>>> 1) Already reached consensus. >>>> 2) Already were sent to the board with the relevant reports. >>>> >>>> So from that perspective, with ?basically administrative? I >>>> mean that there is not ?a lot of other? work to be done in >>>> the proposals. Of course, the board should make sure that >>>> the proposals aren?t against the company, but the legal >>>> implications, operational feasibility, alignment with the >>>> bylaws, etc., was already done because all this is part of >>>> the analysis impact that was prepared *before* declaring >>>> consensus. This is just the way the PDP works, so we aren?t >>>> changing anything. >>>> >>>> Saludos, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>>> El 8 oct 2025, a las 18:07, Caleb Ogundele >>>>> escribi?: >>>>> >>>>> Hi Jordi and All, >>>>> >>>>> I'm happy this list is?becoming more active, and it is a >>>>> good thing. >>>>> Responding to @Jordi, I must respectfully differ with >>>>> Jordi on point one. While I share the desire to see >>>>> pending proposals move forward, I don't believe board >>>>> ratification should be characterized as "basically an >>>>> administrative task that should not take too much time." >>>>> >>>>> Board ratification is a critical governance checkpoint >>>>> where proposals are reviewed for legal implications, >>>>> operational feasibility, and alignment with AFRINIC's >>>>> mission and bylaws. Given that we're emerging from three >>>>> years of limited functionality as?a community, I believe >>>>> the Community and the Board deserve adequate time to >>>>> properly review and ratify proposals, especially those >>>>> that may have significant operational or financial >>>>> implications for AFRINIC and its members. Times have >>>>> changed in the last three years and community members have >>>>> different views on certain policies. Rushing this process >>>>> could lead to oversights that create problems down the >>>>> line. Quality should take precedence over speed. >>>>> >>>>> *Caleb Ogundele* >>>>> /Speaking for myself as a community member >>>>> >>>>> >>>>> >>>>> >>>>> / >>>>> >>>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD >>>>> wrote: >>>>> >>>>> HI Seun, all, >>>>> >>>>> Fully agree with your view. I will add 2 more points: >>>>> >>>>> 1) There are several policy proposals that reached >>>>> consensus and are ?paused? just waiting for the board >>>>> ratification. I understand the board will be very >>>>> busy, but the ratification is basically an >>>>> administrative task that should not take too much >>>>> time. So please, consider doing so ASAP, so the >>>>> implementation can also be initiated, as I think in >>>>> some cases it may take long time. >>>>> >>>>> >>>>> 2) Some of use may need to plan ahead, and buy our >>>>> flights as early as possible (too close to the meeting >>>>> become extremely expensive when traveling from abroad) >>>>> for the next PPM, so it will be good to announce firm >>>>> dates and location as soon as possible. >>>>> >>>>> Those that have policy proposals still under >>>>> discussion really need to have a status summary and >>>>> specially understand if the actual co-chairs will >>>>> continue as suggested, so we can restart our work and >>>>> encourage discussions in the community. >>>>> >>>>> Finally, I don?t think we need a ?complete >>>>> modernization of the policy manual?, but instead >>>>> concentrate in review the existing discussion and >>>>> decide if we need to focus on any new topic at the >>>>> time being. >>>>> >>>>> Tks! >>>>> >>>>> Saludos, >>>>> Jordi >>>>> >>>>> @jordipalet >>>>> >>>>> >>>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji >>>>>> escribi?: >>>>>> >>>>>> Hello Ben, RPD >>>>>> >>>>>> It's good that this discussion is starting up. I >>>>>> don't think anything revolutionary with the rpd needs >>>>>> to happen from the board level at this time. The rpd >>>>>> itself should evolve through policies and while the >>>>>> board indeed has the ability to write a policy when >>>>>> required and in certain?circumstances i do think that >>>>>> it isn't necessary at this time. I would suggest the >>>>>> following: >>>>>> >>>>>> 1. Current Co-Chairs continue in their role towards >>>>>> the next Public Policy Meeting (PPM) and they should >>>>>> coordinate on the things Sami mentioned with regards >>>>>> to authors representing their proposal and new >>>>>> proposals as applicable. >>>>>> >>>>>> 2. We usually hold 2 PPMs every year 1 during the AIS >>>>>> and another at the second AFRINIC pubic meeting in >>>>>> the year, it will be good for the Board to provide >>>>>> the rpd with some information on how soon that can >>>>>> happen. >>>>>> >>>>>> 3. With the recent board election, staff does have >>>>>> significant experience on conducting credible and >>>>>> verifiable election. The Board should leverage on >>>>>> that to organise election of Co-Chairs at the next >>>>>> ppm inline with the CPM. The 2 seats should be filled >>>>>> in a staggered manner >>>>>> >>>>>> Regards >>>>>> >>>>>> ---- >>>>>> Sent from my mobile >>>>>> kindly excuse typos >>>>>> >>>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via >>>>>> RPD, wrote: >>>>>> >>>>>> Sami, >>>>>> Thanks for your mail and we appreciate your >>>>>> contributions to PWDG to date and are happy to >>>>>> see you are keen to start it up again. I am >>>>>> replying as a community member, though I am also >>>>>> a board member of AfriNIC. >>>>>> >>>>>> I feel that as we restart the PWDG process, what >>>>>> is absolutely key is that we get *much more* >>>>>> diversity in that process. My question back to >>>>>> you is to ask, how do we invigorate the process >>>>>> to involve many more key experts in the digital >>>>>> economy of Africa? >>>>>> >>>>>> Kind regards >>>>>> Ben >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board >>>>>>> wrote: >>>>>>> >>>>>>> ? >>>>>>> *Dear PDWG Community,* >>>>>>> * >>>>>>> * >>>>>>> I hope this message finds you well. >>>>>>> >>>>>>> I would like to take this opportunity to >>>>>>> congratulate you all on the successful election >>>>>>> of the AFRINIC Board and the resumption of its >>>>>>> proper functioning. This milestone marks an >>>>>>> important step toward restoring stability, >>>>>>> trust, and continuity in AFRINIC?s role as the >>>>>>> Regional Internet Registry for Africa. With >>>>>>> governance now back on track, it is the right >>>>>>> moment to resume the Policy Development Process >>>>>>> (PDP) and address the policy gaps that have >>>>>>> accumulated during the past three years of >>>>>>> interruption. >>>>>>> >>>>>>> As you are aware, over the past three years >>>>>>> AFRINIC has gone through a period of limited >>>>>>> functionality, and the Policy Development >>>>>>> Process (PDP) has been effectively paused. >>>>>>> During this time, the global Internet number >>>>>>> community has continued to evolve, with >>>>>>> significant policy updates taking place across >>>>>>> the other RIRs. This has created a widening gap >>>>>>> between AFRINIC?s Consolidated Policy Manual >>>>>>> (CPM) and those of our sister RIRs. >>>>>>> >>>>>>> In order to restore the momentum of policy >>>>>>> development in our region and to ensure that >>>>>>> AFRINIC?s policy environment remains relevant, >>>>>>> consistent, and globally aligned, I would like >>>>>>> to highlight the following areas where action is >>>>>>> needed: >>>>>>> >>>>>>> *Previous PDWG Co-Chairs* >>>>>>> While their terms have now ended, we request >>>>>>> that the most recent PDWG Co-Chairs prepare a >>>>>>> short report summarizing the last set of policy >>>>>>> proposals that were under discussion before the >>>>>>> process stalled. We further encourage the >>>>>>> original authors of those drafts to resubmit >>>>>>> them for renewed community review, or >>>>>>> alternatively, invite any community member to >>>>>>> take initiative to re-submit and champion them. >>>>>>> >>>>>>> *AFRINIC Board* >>>>>>> We call on the Board to formally publish a >>>>>>> community call for modernizing the AFRINIC >>>>>>> Policy Manual. This would include identifying >>>>>>> and prioritizing areas where policy alignment >>>>>>> with other RIRs is needed (e.g., IPv4 transfer >>>>>>> frameworks, IPv6 allocation criteria, RPKI >>>>>>> adoption, Whois/privacy reforms, and >>>>>>> membership/resource governance models). Such a >>>>>>> call would help set a clear direction and >>>>>>> provide legitimacy to the process of catching up >>>>>>> with global best practices. >>>>>>> >>>>>>> *PDWG Community* >>>>>>> Most importantly, we urge all community members >>>>>>> to actively re-engage in the PDP by discussing >>>>>>> any submitted proposals, providing constructive >>>>>>> feedback, and enriching the drafts with insights >>>>>>> drawn from operational experience. The strength >>>>>>> of AFRINIC?s PDP has always been rooted in the >>>>>>> diversity and expertise of its community, and >>>>>>> your participation will be crucial in shaping >>>>>>> the future of Internet number resource >>>>>>> management in our region. >>>>>>> >>>>>>> This is a collective responsibility, and now is >>>>>>> the right moment to re-energize our PDP and >>>>>>> demonstrate the resilience of the AFRINIC community. >>>>>>> >>>>>>> With Regards. >>>>>>> >>>>>>> *Sami Salih*, PhD (ICT), PMP? >>>>>>> Assistant Professor, Sudan University of Science >>>>>>> and Technology >>>>>>> Tel: (249) 122045707 >>>>>>> _______________________________________________ >>>>>>> Board mailing list -- board at afrinic.net >>>>>>> To unsubscribe send an email to >>>>>>> board-leave at afrinic.net >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> >>>>> ********************************************** >>>>> IPv4 is over >>>>> Are you ready for the new Internet ? >>>>> http://www.theipv6company.com >>>>> The IPv6 Company >>>>> >>>>> This electronic message contains information which may >>>>> be privileged or confidential. The information is >>>>> intended to be for the exclusive use of the >>>>> individual(s) named above and further non-explicilty >>>>> authorized disclosure, copying, distribution or use of >>>>> the contents of this information, even if partially, >>>>> including attached files, is strictly prohibited and >>>>> will be considered a criminal offense. If you are not >>>>> the intended recipient be aware that any disclosure, >>>>> copying, distribution or use of the contents of this >>>>> information, even if partially, including attached >>>>> files, is strictly prohibited, will be considered a >>>>> criminal offense, so you must reply to the original >>>>> sender to inform about this communication and delete it. >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> >>>>> >>>>> -- >>>>> *Caleb Ogundele* >>>>> Email: muyiwacaleb at gmail.com >>>> >>>> >>>> ********************************************** >>>> IPv4 is over >>>> Are you ready for the new Internet ? >>>> http://www.theipv6company.com >>>> The IPv6 Company >>>> >>>> This electronic message contains information which may be >>>> privileged or confidential. The information is intended to >>>> be for the exclusive use of the individual(s) named above >>>> and further non-explicilty authorized disclosure, copying, >>>> distribution or use of the contents of this information, >>>> even if partially, including attached files, is strictly >>>> prohibited and will be considered a criminal offense. If >>>> you are not the intended recipient be aware that any >>>> disclosure, copying, distribution or use of the contents of >>>> this information, even if partially, including attached >>>> files, is strictly prohibited, will be considered a >>>> criminal offense, so you must reply to the original sender >>>> to inform about this communication and delete it. >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be >> privileged or confidential. The information is intended to be for >> the exclusive use of the individual(s) named above and further >> non-explicilty authorized disclosure, copying, distribution or >> use of the contents of this information, even if partially, >> including attached files, is strictly prohibited and will be >> considered a criminal offense. If you are not the intended >> recipient be aware that any disclosure, copying, distribution or >> use of the contents of this information, even if partially, >> including attached files, is strictly prohibited, will be >> considered a criminal offense, so you must reply to the original >> sender to inform about this communication and delete it. >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From mamattah.raymond at gmail.com Fri Oct 10 09:17:34 2025 From: mamattah.raymond at gmail.com (Raymond Mamattah) Date: Fri, 10 Oct 2025 09:17:34 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: Hi Jacob, Thank you reiterated what I mentioned in my email. Cheers, --- Raymond Mamattah Accra, Ghana ?? On Fri, 10 Oct 2025, 09:12 Jaco Kroon, wrote: > Hi Raymond, > > Jordi is right in that once policies have been passed to the board it's > not really trivial for them to push it back to the PDP, and Jordi is also > right in that "what gives them the right?" (which is what I paraphrased > from his writing). That's a very valid question. > > I would personally rather have the board be on the side of caution, and > send everything back to the chairs to revalidate, as new inputs from the > last couple of years may very well result in a different impact assessment. > > I do also think that going forward we need to have a legal assessment on > all new policies too - even if (in my made up estimation) the far bulk of > policies will not have legal implications, however, contracts may be > impacted by policies. Specifically, some of the sticky points that came up > in discussion: > > 1. Can rule/policy changes be enforced retroactively? > 2. If a contract specifically states you're allowed to do xyz, does that > preclude everything else, or is only what is specifically precluded > contractually precluded? > > To make this even more sticky, let's say that a new policy takes away a > right you previously had (implied or otherwise, for example, the topic of > whether you're allowed to lease/sell/broker Afrinic IPv4 space, which is > hotly debated with some saying you're allowed to and some saying you're not > - I have my opinions on this but that's orthogonal to discussion I'm trying > to have so please treat it as an example and not the topic), is that > enforceable? > > What if a new policy/rule gives you a new right you didn't have previously? > > Clearly there are potentially legal implications here that can (and > plainly has) negatively impacted the company (Afrinic). And hopefully it's > clear that the answers are not clear cut black and white, even though we'd > like them to be. > > I think given the above a pause is in order to allow a re-assessment of > all policies that has been submitted to board for ratification. > > I would also like to know if there is a list of such policies, and where > it can be found, or if one of the staff members are possibly in a position > to provide such a list, along with the wording impact on the CPM and the > impact assessments that were provided. > > This should allow the PDWG to quickly state "we're OK with these > proceeding, we'd like these back" etc ... assuming no one points out a > policy issue with what I'm proposing. > > Kind regards, > Jaco > On 2025/10/10 10:43, Raymond Mamattah wrote: > > Great discussions! > > My one cent is that due to the impasse we have had, which is due partly to > AFRINIC's own by-laws/policies, I think the Board would have to look > critically and with multiple checks before ratifying any policy. > > I also think we should not push for a policy that's not already passed to > be hurriedly ratified. Ideally such policies should go through "public > comments" for critical checks before being passed on for ratification. > > Care must be taken so we don't have a "stone-around our neck to make us > easily sink" again. > > Regards, > > --- > Raymond Mamattah > Accra, Ghana ?? > > On Fri, 10 Oct 2025, 08:10 Jaco Kroon, wrote: > >> Hi Jordi, >> >> I fully agree with what you say here. >> >> There are however pending disputes regarding legitimacy of a couple of >> members who could use the specific policy to sidestep the issue. The >> policy needs to be adjusted to ensure that only members who's not only in >> good standing, but who is fully compliant with existing policies and where >> there are no ongoing disputes/court cases etc ... are allowed to transfer >> out. >> >> Kind regards, >> Jaco >> On 2025/10/09 17:10, jordi.palet--- via RPD wrote: >> >> I don?t think membership status has anything to do with PDP. >> >> Ideally PDP is contributed by many members actively participating, but I >> think this is not the case (not only in Afrinic, also in general in other >> RIRs). >> >> Even if I personally disagree with the transfer policy that got consensus >> declared, I think it should be ratified immediately, because implementation >> takes many months (as experienced by other RIRs). In that period, we still >> have the chance to improve it, if the community believe that needs to be >> done. Then small implementation changes can often be done very quickly. >> >> This is the same for any policy that reached consensus, even for the >> complete policy manual. It is a ?live law?, the community has the chance >> to*always* change or improve things. What it will be useless and long time >> consuming is when something that reached consensus (and had a positive >> impact analisys) is returned to the list to re-start again the full >> process. Again, if something can be improved, let?s do it based on the >> already approved text, not from scracth. >> >> Regards, >> Jordi >> >> @jordipalet >> >> >> El 9 oct 2025, a las 6:42, Jaco Kroon >> escribi?: >> >> Hi, >> >> That policy specifically may be one we may want to hold off until current >> membership status has been sorted out first. Or at least the policy should >> be amended to compensate for what we've learned in the last five years. >> >> Kind regards, >> Jaco >> >> On 2025/10/09 02:21, Emmanuel Vitus wrote: >> >> Good to see the list active again. Hopefully we can keep the energy >> focused this time and not fall back into the long circular debates we had >> in the past. >> It could help to have a simple matrix showing which proposals can be >> ratified quickly with little or no cost and which ones may need more time >> or legal review. A timeline would also be useful to follow progress taking >> into account the Board comments and the steps before ratification. >> The transfer policy should move forward as soon as possible, my 2cents. >> Cheers! >> >> - Emmanuel >> >> Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD a >> ?crit : >> >>> Hi Caleb, >>> >>> The proposals that I refer: >>> 1) Already reached consensus. >>> 2) Already were sent to the board with the relevant reports. >>> >>> So from that perspective, with ?basically administrative? I mean that >>> there is not ?a lot of other? work to be done in the proposals. Of course, >>> the board should make sure that the proposals aren?t against the company, >>> but the legal implications, operational feasibility, alignment with the >>> bylaws, etc., was already done because all this is part of the analysis >>> impact that was prepared *before* declaring consensus. This is just the way >>> the PDP works, so we aren?t changing anything. >>> >>> Saludos, >>> Jordi >>> >>> @jordipalet >>> >>> >>> El 8 oct 2025, a las 18:07, Caleb Ogundele >>> escribi?: >>> >>> Hi Jordi and All, >>> >>> I'm happy this list is becoming more active, and it is a good thing. >>> Responding to @Jordi, I must respectfully differ with Jordi on point >>> one. While I share the desire to see pending proposals move forward, I >>> don't believe board ratification should be characterized as "basically an >>> administrative task that should not take too much time." >>> >>> Board ratification is a critical governance checkpoint where proposals >>> are reviewed for legal implications, operational feasibility, and alignment >>> with AFRINIC's mission and bylaws. Given that we're emerging from three >>> years of limited functionality as a community, I believe the Community and >>> the Board deserve adequate time to properly review and ratify proposals, >>> especially those that may have significant operational or financial >>> implications for AFRINIC and its members. Times have changed in the last >>> three years and community members have different views on certain policies. >>> Rushing this process could lead to oversights that create problems down the >>> line. Quality should take precedence over speed. >>> *Caleb Ogundele* >>> >>> >>> >>> >>> >>> *Speaking for myself as a community member * >>> >>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD >>> wrote: >>> >>>> HI Seun, all, >>>> >>>> Fully agree with your view. I will add 2 more points: >>>> >>>> 1) There are several policy proposals that reached consensus and are >>>> ?paused? just waiting for the board ratification. I understand the board >>>> will be very busy, but the ratification is basically an administrative task >>>> that should not take too much time. So please, consider doing so ASAP, so >>>> the implementation can also be initiated, as I think in some cases it may >>>> take long time. >>>> >>>> >>> 2) Some of use may need to plan ahead, and buy our flights as early as >>>> possible (too close to the meeting become extremely expensive when >>>> traveling from abroad) for the next PPM, so it will be good to announce >>>> firm dates and location as soon as possible. >>>> >>>> Those that have policy proposals still under discussion really need to >>>> have a status summary and specially understand if the actual co-chairs will >>>> continue as suggested, so we can restart our work and encourage discussions >>>> in the community. >>>> >>>> Finally, I don?t think we need a ?complete modernization of the policy >>>> manual?, but instead concentrate in review the existing discussion and >>>> decide if we need to focus on any new topic at the time being. >>>> >>>> Tks! >>>> >>>> Saludos, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>> El 8 oct 2025, a las 17:02, Seun Ojedeji >>>> escribi?: >>>> >>>> Hello Ben, RPD >>>> >>>> It's good that this discussion is starting up. I don't think anything >>>> revolutionary with the rpd needs to happen from the board level at this >>>> time. The rpd itself should evolve through policies and while the board >>>> indeed has the ability to write a policy when required and in >>>> certain circumstances i do think that it isn't necessary at this time. I >>>> would suggest the following: >>>> >>>> 1. Current Co-Chairs continue in their role towards the next Public >>>> Policy Meeting (PPM) and they should coordinate on the things Sami >>>> mentioned with regards to authors representing their proposal and new >>>> proposals as applicable. >>>> >>>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at >>>> the second AFRINIC pubic meeting in the year, it will be good for the Board >>>> to provide the rpd with some information on how soon that can happen. >>>> >>>> 3. With the recent board election, staff does have significant >>>> experience on conducting credible and verifiable election. The Board should >>>> leverage on that to organise election of Co-Chairs at the next ppm inline >>>> with the CPM. The 2 seats should be filled in a staggered manner >>>> >>>> Regards >>>> >>>> ---- >>>> Sent from my mobile >>>> kindly excuse typos >>>> >>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, < >>>> rpd at afrinic.net> wrote: >>>> >>>>> Sami, >>>>> Thanks for your mail and we appreciate your contributions to PWDG to >>>>> date and are happy to see you are keen to start it up again. I am replying >>>>> as a community member, though I am also a board member of AfriNIC. >>>>> >>>>> I feel that as we restart the PWDG process, what is absolutely key is >>>>> that we get *much more* diversity in that process. My question back >>>>> to you is to ask, how do we invigorate the process to involve many more key >>>>> experts in the digital economy of Africa? >>>>> >>>>> Kind regards >>>>> Ben >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board >>>>> wrote: >>>>> >>>>> ? >>>>> *Dear PDWG Community,* >>>>> >>>>> I hope this message finds you well. >>>>> >>>>> I would like to take this opportunity to congratulate you all on the >>>>> successful election of the AFRINIC Board and the resumption of its proper >>>>> functioning. This milestone marks an important step toward restoring >>>>> stability, trust, and continuity in AFRINIC?s role as the Regional Internet >>>>> Registry for Africa. With governance now back on track, it is the right >>>>> moment to resume the Policy Development Process (PDP) and address the >>>>> policy gaps that have accumulated during the past three years of >>>>> interruption. >>>>> >>>>> As you are aware, over the past three years AFRINIC has gone through a >>>>> period of limited functionality, and the Policy Development Process (PDP) >>>>> has been effectively paused. During this time, the global Internet number >>>>> community has continued to evolve, with significant policy updates taking >>>>> place across the other RIRs. This has created a widening gap between >>>>> AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>> >>>>> In order to restore the momentum of policy development in our region >>>>> and to ensure that AFRINIC?s policy environment remains relevant, >>>>> consistent, and globally aligned, I would like to highlight the following >>>>> areas where action is needed: >>>>> >>>>> *Previous PDWG Co-Chairs* >>>>> While their terms have now ended, we request that the most recent PDWG >>>>> Co-Chairs prepare a short report summarizing the last set of policy >>>>> proposals that were under discussion before the process stalled. We further >>>>> encourage the original authors of those drafts to resubmit them for renewed >>>>> community review, or alternatively, invite any community member to take >>>>> initiative to re-submit and champion them. >>>>> >>>>> *AFRINIC Board* >>>>> We call on the Board to formally publish a community call for >>>>> modernizing the AFRINIC Policy Manual. This would include identifying and >>>>> prioritizing areas where policy alignment with other RIRs is needed (e.g., >>>>> IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, >>>>> Whois/privacy reforms, and membership/resource governance models). Such a >>>>> call would help set a clear direction and provide legitimacy to the process >>>>> of catching up with global best practices. >>>>> >>>>> *PDWG Community* >>>>> Most importantly, we urge all community members to actively re-engage >>>>> in the PDP by discussing any submitted proposals, providing constructive >>>>> feedback, and enriching the drafts with insights drawn from operational >>>>> experience. The strength of AFRINIC?s PDP has always been rooted in the >>>>> diversity and expertise of its community, and your participation will be >>>>> crucial in shaping the future of Internet number resource management in our >>>>> region. >>>>> >>>>> This is a collective responsibility, and now is the right moment to >>>>> re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>> >>>>> With Regards. >>>>> >>>>> *Sami Salih*, PhD (ICT), PMP? >>>>> Assistant Professor, Sudan University of Science and Technology >>>>> Tel: (249) 122045707 >>>>> _______________________________________________ >>>>> Board mailing list -- board at afrinic.net >>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> >>>> ********************************************** >>>> IPv4 is over >>>> Are you ready for the new Internet ? >>>> http://www.theipv6company.com >>>> The IPv6 Company >>>> >>>> This electronic message contains information which may be privileged or >>>> confidential. The information is intended to be for the exclusive use of >>>> the individual(s) named above and further non-explicilty authorized >>>> disclosure, copying, distribution or use of the contents of this >>>> information, even if partially, including attached files, is strictly >>>> prohibited and will be considered a criminal offense. If you are not the >>>> intended recipient be aware that any disclosure, copying, distribution or >>>> use of the contents of this information, even if partially, including >>>> attached files, is strictly prohibited, will be considered a criminal >>>> offense, so you must reply to the original sender to inform about this >>>> communication and delete it. >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>> >>> >>> -- >>> *Caleb Ogundele* >>> Email: muyiwacaleb at gmail.com >>> >>> >>> >>> ********************************************** >>> IPv4 is over >>> Are you ready for the new Internet ? >>> http://www.theipv6company.com >>> The IPv6 Company >>> >>> This electronic message contains information which may be privileged or >>> confidential. The information is intended to be for the exclusive use of >>> the individual(s) named above and further non-explicilty authorized >>> disclosure, copying, distribution or use of the contents of this >>> information, even if partially, including attached files, is strictly >>> prohibited and will be considered a criminal offense. If you are not the >>> intended recipient be aware that any disclosure, copying, distribution or >>> use of the contents of this information, even if partially, including >>> attached files, is strictly prohibited, will be considered a criminal >>> offense, so you must reply to the original sender to inform about this >>> communication and delete it. >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> >> _______________________________________________ >> RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd >> >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or >> confidential. The information is intended to be for the exclusive use of >> the individual(s) named above and further non-explicilty authorized >> disclosure, copying, distribution or use of the contents of this >> information, even if partially, including attached files, is strictly >> prohibited and will be considered a criminal offense. If you are not the >> intended recipient be aware that any disclosure, copying, distribution or >> use of the contents of this information, even if partially, including >> attached files, is strictly prohibited, will be considered a criminal >> offense, so you must reply to the original sender to inform about this >> communication and delete it. >> >> >> _______________________________________________ >> RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > > _______________________________________________ > RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From saul at enetworks.co.za Fri Oct 10 12:29:00 2025 From: saul at enetworks.co.za (Saul Stein) Date: Fri, 10 Oct 2025 12:29:00 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: Jaco raises a good point? From: Jaco Kroon Sent: Friday, 10 October 2025 10:06 To: jordi.palet at consulintel.es; rpd Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual Hi Jordi, I fully agree with what you say here. There are however pending disputes regarding legitimacy of a couple of members who could use the specific policy to sidestep the issue. The policy needs to be adjusted to ensure that only members who's not only in good standing, but who is fully compliant with existing policies and where there are no ongoing disputes/court cases etc ... are allowed to transfer out. Kind regards, Jaco On 2025/10/09 17:10, jordi.palet--- via RPD wrote: I don?t think membership status has anything to do with PDP. Ideally PDP is contributed by many members actively participating, but I think this is not the case (not only in Afrinic, also in general in other RIRs). Even if I personally disagree with the transfer policy that got consensus declared, I think it should be ratified immediately, because implementation takes many months (as experienced by other RIRs). In that period, we still have the chance to improve it, if the community believe that needs to be done. Then small implementation changes can often be done very quickly. This is the same for any policy that reached consensus, even for the complete policy manual. It is a ?live law?, the community has the chance to*always* change or improve things. What it will be useless and long time consuming is when something that reached consensus (and had a positive impact analisys) is returned to the list to re-start again the full process. Again, if something can be improved, let?s do it based on the already approved text, not from scracth. Regards, Jordi @jordipalet El 9 oct 2025, a las 6:42, Jaco Kroon escribi?: Hi, That policy specifically may be one we may want to hold off until current membership status has been sorted out first. Or at least the policy should be amended to compensate for what we've learned in the last five years. Kind regards, Jaco On 2025/10/09 02:21, Emmanuel Vitus wrote: Good to see the list active again. Hopefully we can keep the energy focused this time and not fall back into the long circular debates we had in the past. It could help to have a simple matrix showing which proposals can be ratified quickly with little or no cost and which ones may need more time or legal review. A timeline would also be useful to follow progress taking into account the Board comments and the steps before ratification. The transfer policy should move forward as soon as possible, my 2cents. Cheers! - Emmanuel Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD > a ?crit : Hi Caleb, The proposals that I refer: 1) Already reached consensus. 2) Already were sent to the board with the relevant reports. So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. Saludos, Jordi @jordipalet El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: Hi Jordi and All, I'm happy this list is becoming more active, and it is a good thing. Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. Caleb Ogundele Speaking for myself as a community member On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: HI Seun, all, Fully agree with your view. I will add 2 more points: 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. Tks! Saludos, Jordi @jordipalet El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: Hello Ben, RPD It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner Regards ---- Sent from my mobile kindly excuse typos On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: Sami, Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? Kind regards Ben Sent from my iPhone On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: ? Dear PDWG Community, I hope this message finds you well. I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: Previous PDWG Co-Chairs While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. AFRINIC Board We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. PDWG Community Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. With Regards. Sami Salih, PhD (ICT), PMP? Assistant Professor, Sudan University of Science and Technology Tel: (249) 122045707 _______________________________________________ Board mailing list -- board at afrinic.net To unsubscribe send an email to board-leave at afrinic.net _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -- Caleb Ogundele Email: muyiwacaleb at gmail.com ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Fri Oct 10 12:33:20 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Fri, 10 Oct 2025 06:33:20 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: Now I understand what you mean. However, the transfers policy will need several months of work for the implementation, so even if ratified will not work immediately. In addition to that, to be able to transfer resources, they must not be in dispute, which clearly is not the case for those cases, right? Saludos, Jordi @jordipalet > El 10 oct 2025, a las 2:06, Jaco Kroon escribi?: > > Hi Jordi, > > I fully agree with what you say here. > > There are however pending disputes regarding legitimacy of a couple of members who could use the specific policy to sidestep the issue. The policy needs to be adjusted to ensure that only members who's not only in good standing, but who is fully compliant with existing policies and where there are no ongoing disputes/court cases etc ... are allowed to transfer out. > > Kind regards, > Jaco > > On 2025/10/09 17:10, jordi.palet--- via RPD wrote: >> I don?t think membership status has anything to do with PDP. >> >> Ideally PDP is contributed by many members actively participating, but I think this is not the case (not only in Afrinic, also in general in other RIRs). >> >> Even if I personally disagree with the transfer policy that got consensus declared, I think it should be ratified immediately, because implementation takes many months (as experienced by other RIRs). In that period, we still have the chance to improve it, if the community believe that needs to be done. Then small implementation changes can often be done very quickly. >> >> This is the same for any policy that reached consensus, even for the complete policy manual. It is a ?live law?, the community has the chance to*always* change or improve things. What it will be useless and long time consuming is when something that reached consensus (and had a positive impact analisys) is returned to the list to re-start again the full process. Again, if something can be improved, let?s do it based on the already approved text, not from scracth. >> >> Regards, >> Jordi >> >> @jordipalet >> >> >>> El 9 oct 2025, a las 6:42, Jaco Kroon escribi?: >>> >>> Hi, >>> >>> That policy specifically may be one we may want to hold off until current membership status has been sorted out first. Or at least the policy should be amended to compensate for what we've learned in the last five years. >>> >>> Kind regards, >>> Jaco >>> >>> On 2025/10/09 02:21, Emmanuel Vitus wrote: >>> >>>> Good to see the list active again. Hopefully we can keep the energy focused this time and not fall back into the long circular debates we had in the past. >>>> It could help to have a simple matrix showing which proposals can be ratified quickly with little or no cost and which ones may need more time or legal review. A timeline would also be useful to follow progress taking into account the Board comments and the steps before ratification. >>>> The transfer policy should move forward as soon as possible, my 2cents. >>>> Cheers! >>>> >>>> - Emmanuel >>>> >>>> Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD > a ?crit : >>>>> Hi Caleb, >>>>> >>>>> The proposals that I refer: >>>>> 1) Already reached consensus. >>>>> 2) Already were sent to the board with the relevant reports. >>>>> >>>>> So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. >>>>> >>>>> Saludos, >>>>> Jordi >>>>> >>>>> @jordipalet >>>>> >>>>> >>>>>> El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: >>>>>> >>>>>> Hi Jordi and All, >>>>>> >>>>>> I'm happy this list is becoming more active, and it is a good thing. >>>>>> Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." >>>>>> Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. >>>>>> >>>>>> Caleb Ogundele >>>>>> Speaking for myself as a community member >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >>>>>>> HI Seun, all, >>>>>>> >>>>>>> Fully agree with your view. I will add 2 more points: >>>>>>> >>>>>>> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >>>>>>> >>>>>> >>>>>>> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >>>>>>> >>>>>>> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >>>>>>> >>>>>>> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >>>>>>> >>>>>>> Tks! >>>>>>> >>>>>>> Saludos, >>>>>>> Jordi >>>>>>> >>>>>>> @jordipalet >>>>>>> >>>>>>> >>>>>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>>>>>>> >>>>>>>> Hello Ben, RPD >>>>>>>> >>>>>>>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>>>>>>> >>>>>>>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>>>>>>> >>>>>>>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>>>>>>> >>>>>>>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>>>>>>> >>>>>>>> Regards >>>>>>>> >>>>>>>> ---- >>>>>>>> Sent from my mobile >>>>>>>> kindly excuse typos >>>>>>>> >>>>>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>>>>>>>> Sami, >>>>>>>>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>>>>>>>> >>>>>>>>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>>>>>>>> >>>>>>>>> Kind regards >>>>>>>>> Ben >>>>>>>>> >>>>>>>>> Sent from my iPhone >>>>>>>>> >>>>>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>>>>>>>> >>>>>>>>>> ? >>>>>>>>>> Dear PDWG Community, >>>>>>>>>> >>>>>>>>>> I hope this message finds you well. >>>>>>>>>> >>>>>>>>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>>>>>>>> >>>>>>>>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>>>>>>> >>>>>>>>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>>>>>>>> >>>>>>>>>> Previous PDWG Co-Chairs >>>>>>>>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>>>>>>>> >>>>>>>>>> AFRINIC Board >>>>>>>>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>>>>>>>> >>>>>>>>>> PDWG Community >>>>>>>>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>>>>>>>> >>>>>>>>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>>>>>>> >>>>>>>>>> With Regards. >>>>>>>>>> >>>>>>>>>> Sami Salih, PhD (ICT), PMP? >>>>>>>>>> Assistant Professor, Sudan University of Science and Technology >>>>>>>>>> Tel: (249) 122045707 >>>>>>>>>> _______________________________________________ >>>>>>>>>> Board mailing list -- board at afrinic.net >>>>>>>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>>>>>> _______________________________________________ >>>>>>>>> RPD mailing list >>>>>>>>> RPD at afrinic.net >>>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>>> _______________________________________________ >>>>>>>> RPD mailing list >>>>>>>> RPD at afrinic.net >>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>> >>>>>>> >>>>>>> ********************************************** >>>>>>> IPv4 is over >>>>>>> Are you ready for the new Internet ? >>>>>>> http://www.theipv6company.com >>>>>>> The IPv6 Company >>>>>>> >>>>>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Caleb Ogundele >>>>>> Email: muyiwacaleb at gmail.com >>>>> >>>>> ********************************************** >>>>> IPv4 is over >>>>> Are you ready for the new Internet ? >>>>> http://www.theipv6company.com >>>>> The IPv6 Company >>>>> >>>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Fri Oct 10 12:34:51 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Fri, 10 Oct 2025 06:34:51 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: <4FD0FD00-F333-4D6A-9D11-AA490916C7D9@consulintel.es> Doing so means we are changing the PDP ?on the fly?, which is against the PDP. Saludos, Jordi @jordipalet > El 10 oct 2025, a las 2:43, Raymond Mamattah escribi?: > > Great discussions! > > My one cent is that due to the impasse we have had, which is due partly to AFRINIC's own by-laws/policies, I think the Board would have to look critically and with multiple checks before ratifying any policy. > > I also think we should not push for a policy that's not already passed to be hurriedly ratified. Ideally such policies should go through "public comments" for critical checks before being passed on for ratification. > > Care must be taken so we don't have a "stone-around our neck to make us easily sink" again. > > Regards, > > --- > Raymond Mamattah > Accra, Ghana ?? > > On Fri, 10 Oct 2025, 08:10 Jaco Kroon, > wrote: >> Hi Jordi, >> >> I fully agree with what you say here. >> >> There are however pending disputes regarding legitimacy of a couple of members who could use the specific policy to sidestep the issue. The policy needs to be adjusted to ensure that only members who's not only in good standing, but who is fully compliant with existing policies and where there are no ongoing disputes/court cases etc ... are allowed to transfer out. >> >> Kind regards, >> Jaco >> >> On 2025/10/09 17:10, jordi.palet--- via RPD wrote: >>> I don?t think membership status has anything to do with PDP. >>> >>> Ideally PDP is contributed by many members actively participating, but I think this is not the case (not only in Afrinic, also in general in other RIRs). >>> >>> Even if I personally disagree with the transfer policy that got consensus declared, I think it should be ratified immediately, because implementation takes many months (as experienced by other RIRs). In that period, we still have the chance to improve it, if the community believe that needs to be done. Then small implementation changes can often be done very quickly. >>> >>> This is the same for any policy that reached consensus, even for the complete policy manual. It is a ?live law?, the community has the chance to*always* change or improve things. What it will be useless and long time consuming is when something that reached consensus (and had a positive impact analisys) is returned to the list to re-start again the full process. Again, if something can be improved, let?s do it based on the already approved text, not from scracth. >>> >>> Regards, >>> Jordi >>> >>> @jordipalet >>> >>> >>>> El 9 oct 2025, a las 6:42, Jaco Kroon escribi?: >>>> >>>> Hi, >>>> >>>> That policy specifically may be one we may want to hold off until current membership status has been sorted out first. Or at least the policy should be amended to compensate for what we've learned in the last five years. >>>> >>>> Kind regards, >>>> Jaco >>>> >>>> On 2025/10/09 02:21, Emmanuel Vitus wrote: >>>> >>>>> Good to see the list active again. Hopefully we can keep the energy focused this time and not fall back into the long circular debates we had in the past. >>>>> It could help to have a simple matrix showing which proposals can be ratified quickly with little or no cost and which ones may need more time or legal review. A timeline would also be useful to follow progress taking into account the Board comments and the steps before ratification. >>>>> The transfer policy should move forward as soon as possible, my 2cents. >>>>> Cheers! >>>>> >>>>> - Emmanuel >>>>> >>>>> Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD > a ?crit : >>>>>> Hi Caleb, >>>>>> >>>>>> The proposals that I refer: >>>>>> 1) Already reached consensus. >>>>>> 2) Already were sent to the board with the relevant reports. >>>>>> >>>>>> So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. >>>>>> >>>>>> Saludos, >>>>>> Jordi >>>>>> >>>>>> @jordipalet >>>>>> >>>>>> >>>>>>> El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: >>>>>>> >>>>>>> Hi Jordi and All, >>>>>>> >>>>>>> I'm happy this list is becoming more active, and it is a good thing. >>>>>>> Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." >>>>>>> Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. >>>>>>> >>>>>>> Caleb Ogundele >>>>>>> Speaking for myself as a community member >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >>>>>>>> HI Seun, all, >>>>>>>> >>>>>>>> Fully agree with your view. I will add 2 more points: >>>>>>>> >>>>>>>> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >>>>>>>> >>>>>>> >>>>>>>> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >>>>>>>> >>>>>>>> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >>>>>>>> >>>>>>>> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >>>>>>>> >>>>>>>> Tks! >>>>>>>> >>>>>>>> Saludos, >>>>>>>> Jordi >>>>>>>> >>>>>>>> @jordipalet >>>>>>>> >>>>>>>> >>>>>>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>>>>>>>> >>>>>>>>> Hello Ben, RPD >>>>>>>>> >>>>>>>>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>>>>>>>> >>>>>>>>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>>>>>>>> >>>>>>>>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>>>>>>>> >>>>>>>>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>>>>>>>> >>>>>>>>> Regards >>>>>>>>> >>>>>>>>> ---- >>>>>>>>> Sent from my mobile >>>>>>>>> kindly excuse typos >>>>>>>>> >>>>>>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>>>>>>>>> Sami, >>>>>>>>>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>>>>>>>>> >>>>>>>>>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>>>>>>>>> >>>>>>>>>> Kind regards >>>>>>>>>> Ben >>>>>>>>>> >>>>>>>>>> Sent from my iPhone >>>>>>>>>> >>>>>>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>>>>>>>>> >>>>>>>>>>> ? >>>>>>>>>>> Dear PDWG Community, >>>>>>>>>>> >>>>>>>>>>> I hope this message finds you well. >>>>>>>>>>> >>>>>>>>>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>>>>>>>>> >>>>>>>>>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>>>>>>>> >>>>>>>>>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>>>>>>>>> >>>>>>>>>>> Previous PDWG Co-Chairs >>>>>>>>>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>>>>>>>>> >>>>>>>>>>> AFRINIC Board >>>>>>>>>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>>>>>>>>> >>>>>>>>>>> PDWG Community >>>>>>>>>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>>>>>>>>> >>>>>>>>>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>>>>>>>> >>>>>>>>>>> With Regards. >>>>>>>>>>> >>>>>>>>>>> Sami Salih, PhD (ICT), PMP? >>>>>>>>>>> Assistant Professor, Sudan University of Science and Technology >>>>>>>>>>> Tel: (249) 122045707 >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Board mailing list -- board at afrinic.net >>>>>>>>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>>>>>>> _______________________________________________ >>>>>>>>>> RPD mailing list >>>>>>>>>> RPD at afrinic.net >>>>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>>>> _______________________________________________ >>>>>>>>> RPD mailing list >>>>>>>>> RPD at afrinic.net >>>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>>> >>>>>>>> >>>>>>>> ********************************************** >>>>>>>> IPv4 is over >>>>>>>> Are you ready for the new Internet ? >>>>>>>> http://www.theipv6company.com >>>>>>>> The IPv6 Company >>>>>>>> >>>>>>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> RPD mailing list >>>>>>>> RPD at afrinic.net >>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Caleb Ogundele >>>>>>> Email: muyiwacaleb at gmail.com >>>>>> >>>>>> ********************************************** >>>>>> IPv4 is over >>>>>> Are you ready for the new Internet ? >>>>>> http://www.theipv6company.com >>>>>> The IPv6 Company >>>>>> >>>>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> >>> ********************************************** >>> IPv4 is over >>> Are you ready for the new Internet ? >>> http://www.theipv6company.com >>> The IPv6 Company >>> >>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>> >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Fri Oct 10 12:43:14 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Fri, 10 Oct 2025 06:43:14 -0600 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: <963D75E3-3E70-4FD9-BEE6-954F8288FE94@consulintel.es> When you sign the service agreement to obtain resources in any RIR, you accept to be bind to the policy manual which is a ?live law?, it gets updated at any time and changes apply to all. Otherwise, it will be useless to have a PDP to update the policy manual. So clearly yes to your point 1 and 2. If there was a right to leasing (which was not the case), and policy change to avoid that, it can be enforced, also in the other way around. There is not way, following the PDP, we can do a ?reassessment? of the PDWG opinion, and you also know that it will be difficult to have everyone agreeing. That why the decisions are based in consensus not voting, and consensus has been already determined by the chairs. Delaying the decision for the ratification is a very ugly manipulation of the process because then it means the time expires and the policies are enforced back to the list. This will mean we can?t trust on the new board, which will be a very bad situation. Regards, Jordi @jordipalet > El 10 oct 2025, a las 3:12, Jaco Kroon escribi?: > > Hi Raymond, > > Jordi is right in that once policies have been passed to the board it's not really trivial for them to push it back to the PDP, and Jordi is also right in that "what gives them the right?" (which is what I paraphrased from his writing). That's a very valid question. > > I would personally rather have the board be on the side of caution, and send everything back to the chairs to revalidate, as new inputs from the last couple of years may very well result in a different impact assessment. > > I do also think that going forward we need to have a legal assessment on all new policies too - even if (in my made up estimation) the far bulk of policies will not have legal implications, however, contracts may be impacted by policies. Specifically, some of the sticky points that came up in discussion: > > 1. Can rule/policy changes be enforced retroactively? > 2. If a contract specifically states you're allowed to do xyz, does that preclude everything else, or is only what is specifically precluded contractually precluded? > > To make this even more sticky, let's say that a new policy takes away a right you previously had (implied or otherwise, for example, the topic of whether you're allowed to lease/sell/broker Afrinic IPv4 space, which is hotly debated with some saying you're allowed to and some saying you're not - I have my opinions on this but that's orthogonal to discussion I'm trying to have so please treat it as an example and not the topic), is that enforceable? > > What if a new policy/rule gives you a new right you didn't have previously? > > Clearly there are potentially legal implications here that can (and plainly has) negatively impacted the company (Afrinic). And hopefully it's clear that the answers are not clear cut black and white, even though we'd like them to be. > > I think given the above a pause is in order to allow a re-assessment of all policies that has been submitted to board for ratification. > > I would also like to know if there is a list of such policies, and where it can be found, or if one of the staff members are possibly in a position to provide such a list, along with the wording impact on the CPM and the impact assessments that were provided. > > This should allow the PDWG to quickly state "we're OK with these proceeding, we'd like these back" etc ... assuming no one points out a policy issue with what I'm proposing. > > Kind regards, > Jaco > > On 2025/10/10 10:43, Raymond Mamattah wrote: >> Great discussions! >> >> My one cent is that due to the impasse we have had, which is due partly to AFRINIC's own by-laws/policies, I think the Board would have to look critically and with multiple checks before ratifying any policy. >> >> I also think we should not push for a policy that's not already passed to be hurriedly ratified. Ideally such policies should go through "public comments" for critical checks before being passed on for ratification. >> >> Care must be taken so we don't have a "stone-around our neck to make us easily sink" again. >> >> Regards, >> >> --- >> Raymond Mamattah >> Accra, Ghana ?? >> >> On Fri, 10 Oct 2025, 08:10 Jaco Kroon, > wrote: >>> Hi Jordi, >>> >>> I fully agree with what you say here. >>> >>> There are however pending disputes regarding legitimacy of a couple of members who could use the specific policy to sidestep the issue. The policy needs to be adjusted to ensure that only members who's not only in good standing, but who is fully compliant with existing policies and where there are no ongoing disputes/court cases etc ... are allowed to transfer out. >>> >>> Kind regards, >>> Jaco >>> >>> On 2025/10/09 17:10, jordi.palet--- via RPD wrote: >>>> I don?t think membership status has anything to do with PDP. >>>> >>>> Ideally PDP is contributed by many members actively participating, but I think this is not the case (not only in Afrinic, also in general in other RIRs). >>>> >>>> Even if I personally disagree with the transfer policy that got consensus declared, I think it should be ratified immediately, because implementation takes many months (as experienced by other RIRs). In that period, we still have the chance to improve it, if the community believe that needs to be done. Then small implementation changes can often be done very quickly. >>>> >>>> This is the same for any policy that reached consensus, even for the complete policy manual. It is a ?live law?, the community has the chance to*always* change or improve things. What it will be useless and long time consuming is when something that reached consensus (and had a positive impact analisys) is returned to the list to re-start again the full process. Again, if something can be improved, let?s do it based on the already approved text, not from scracth. >>>> >>>> Regards, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>>> El 9 oct 2025, a las 6:42, Jaco Kroon escribi?: >>>>> >>>>> Hi, >>>>> >>>>> That policy specifically may be one we may want to hold off until current membership status has been sorted out first. Or at least the policy should be amended to compensate for what we've learned in the last five years. >>>>> >>>>> Kind regards, >>>>> Jaco >>>>> >>>>> On 2025/10/09 02:21, Emmanuel Vitus wrote: >>>>> >>>>>> Good to see the list active again. Hopefully we can keep the energy focused this time and not fall back into the long circular debates we had in the past. >>>>>> It could help to have a simple matrix showing which proposals can be ratified quickly with little or no cost and which ones may need more time or legal review. A timeline would also be useful to follow progress taking into account the Board comments and the steps before ratification. >>>>>> The transfer policy should move forward as soon as possible, my 2cents. >>>>>> Cheers! >>>>>> >>>>>> - Emmanuel >>>>>> >>>>>> Le jeu. 9 oct. 2025 ? 00:18, jordi.palet--- via RPD > a ?crit : >>>>>>> Hi Caleb, >>>>>>> >>>>>>> The proposals that I refer: >>>>>>> 1) Already reached consensus. >>>>>>> 2) Already were sent to the board with the relevant reports. >>>>>>> >>>>>>> So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. >>>>>>> >>>>>>> Saludos, >>>>>>> Jordi >>>>>>> >>>>>>> @jordipalet >>>>>>> >>>>>>> >>>>>>>> El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: >>>>>>>> >>>>>>>> Hi Jordi and All, >>>>>>>> >>>>>>>> I'm happy this list is becoming more active, and it is a good thing. >>>>>>>> Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." >>>>>>>> Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. >>>>>>>> >>>>>>>> Caleb Ogundele >>>>>>>> Speaking for myself as a community member >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >>>>>>>>> HI Seun, all, >>>>>>>>> >>>>>>>>> Fully agree with your view. I will add 2 more points: >>>>>>>>> >>>>>>>>> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >>>>>>>>> >>>>>>>> >>>>>>>>> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >>>>>>>>> >>>>>>>>> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >>>>>>>>> >>>>>>>>> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >>>>>>>>> >>>>>>>>> Tks! >>>>>>>>> >>>>>>>>> Saludos, >>>>>>>>> Jordi >>>>>>>>> >>>>>>>>> @jordipalet >>>>>>>>> >>>>>>>>> >>>>>>>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>>>>>>>>> >>>>>>>>>> Hello Ben, RPD >>>>>>>>>> >>>>>>>>>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>>>>>>>>> >>>>>>>>>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>>>>>>>>> >>>>>>>>>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>>>>>>>>> >>>>>>>>>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>>>>>>>>> >>>>>>>>>> Regards >>>>>>>>>> >>>>>>>>>> ---- >>>>>>>>>> Sent from my mobile >>>>>>>>>> kindly excuse typos >>>>>>>>>> >>>>>>>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>>>>>>>>>> Sami, >>>>>>>>>>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>>>>>>>>>> >>>>>>>>>>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>>>>>>>>>> >>>>>>>>>>> Kind regards >>>>>>>>>>> Ben >>>>>>>>>>> >>>>>>>>>>> Sent from my iPhone >>>>>>>>>>> >>>>>>>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>>>>>>>>>> >>>>>>>>>>>> ? >>>>>>>>>>>> Dear PDWG Community, >>>>>>>>>>>> >>>>>>>>>>>> I hope this message finds you well. >>>>>>>>>>>> >>>>>>>>>>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>>>>>>>>>> >>>>>>>>>>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>>>>>>>>> >>>>>>>>>>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>>>>>>>>>> >>>>>>>>>>>> Previous PDWG Co-Chairs >>>>>>>>>>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>>>>>>>>>> >>>>>>>>>>>> AFRINIC Board >>>>>>>>>>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>>>>>>>>>> >>>>>>>>>>>> PDWG Community >>>>>>>>>>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>>>>>>>>>> >>>>>>>>>>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>>>>>>>>> >>>>>>>>>>>> With Regards. >>>>>>>>>>>> >>>>>>>>>>>> Sami Salih, PhD (ICT), PMP? >>>>>>>>>>>> Assistant Professor, Sudan University of Science and Technology >>>>>>>>>>>> Tel: (249) 122045707 >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Board mailing list -- board at afrinic.net >>>>>>>>>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> RPD mailing list >>>>>>>>>>> RPD at afrinic.net >>>>>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>>>>> _______________________________________________ >>>>>>>>>> RPD mailing list >>>>>>>>>> RPD at afrinic.net >>>>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>>>> >>>>>>>>> >>>>>>>>> ********************************************** >>>>>>>>> IPv4 is over >>>>>>>>> Are you ready for the new Internet ? >>>>>>>>> http://www.theipv6company.com >>>>>>>>> The IPv6 Company >>>>>>>>> >>>>>>>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> RPD mailing list >>>>>>>>> RPD at afrinic.net >>>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Caleb Ogundele >>>>>>>> Email: muyiwacaleb at gmail.com >>>>>>> >>>>>>> ********************************************** >>>>>>> IPv4 is over >>>>>>> Are you ready for the new Internet ? >>>>>>> http://www.theipv6company.com >>>>>>> The IPv6 Company >>>>>>> >>>>>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> ********************************************** >>>> IPv4 is over >>>> Are you ready for the new Internet ? >>>> http://www.theipv6company.com >>>> The IPv6 Company >>>> >>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>> >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Fri Oct 10 12:47:40 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Fri, 10 Oct 2025 14:47:40 +0200 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> Message-ID: <1466a993-5cfe-4965-95e8-7b220670ce37@uls.co.za> Hi Jordi, That may be true.? But I'd prefer to re-look at the wording of the policy to be sure regardless. A few months ... vs an issue that has dragged on for years. Kind regards, Jaco On 2025/10/10 14:33, jordi.palet--- via RPD wrote: > Now I understand what you mean. However, the transfers policy will > need several months of work for the implementation, so even if > ratified will not work immediately. > > In addition to that, to be able to transfer resources, they must not > be in dispute, which clearly is not the case for those cases, right? > > > Saludos, > Jordi > > @jordipalet > > >> El 10 oct 2025, a las 2:06, Jaco Kroon escribi?: >> >> Hi Jordi, >> >> I fully agree with what you say here. >> >> There are however pending disputes regarding legitimacy of a couple >> of members who could use the specific policy to sidestep the issue.? >> The policy needs to be adjusted to ensure that only members who's not >> only in good standing, but who is fully compliant with existing >> policies and where there are no ongoing disputes/court cases etc ... >> are allowed to transfer out. >> >> Kind regards, >> Jaco >> >> On 2025/10/09 17:10, jordi.palet--- via RPD wrote: >>> I don?t think membership status has anything to do with PDP. >>> >>> Ideally PDP is contributed by many members actively participating, >>> but I think this is not the case (not only in Afrinic, also in >>> general in other RIRs). >>> >>> Even if I personally disagree with the transfer policy that got >>> consensus declared, I think it should be ratified immediately, >>> because implementation takes many months (as experienced by other >>> RIRs). In that period, we still have the chance to improve it, if >>> the community believe that needs to be done. Then small >>> implementation changes can often be done very quickly. >>> >>> This is the same for any policy that reached consensus, even for the >>> complete policy manual. It is a ?live law?, the community has the >>> chance to*always* change or improve things. What it will be useless >>> and long time consuming is when something that reached consensus >>> (and had a positive impact analisys) is returned to the list to >>> re-start again the full process. Again, if something can be >>> improved, let?s do it based on the already approved text, not from >>> scracth. >>> >>> Regards, >>> Jordi >>> >>> @jordipalet >>> >>> >>>> El 9 oct 2025, a las 6:42, Jaco Kroon escribi?: >>>> >>>> Hi, >>>> >>>> That policy specifically may be one we may want to hold off until >>>> current membership status has been sorted out first.? Or at least >>>> the policy should be amended to compensate for what we've learned >>>> in the last five years. >>>> >>>> Kind regards, >>>> Jaco >>>> >>>> On 2025/10/09 02:21, Emmanuel Vitus wrote: >>>> >>>>> Good to see the list active again. Hopefully we can keep the >>>>> energy focused this time and not fall back into the long circular >>>>> debates we had in the past. >>>>> It could help to have a simple matrix showing which proposals can >>>>> be ratified quickly with little or no cost and which ones may need >>>>> more time or legal review. A timeline would also be useful to >>>>> follow progress taking into account the Board comments and the >>>>> steps before ratification. >>>>> The transfer policy should move forward as soon as possible,?my >>>>> 2cents. >>>>> Cheers! >>>>> >>>>> - Emmanuel >>>>> >>>>> Le?jeu. 9 oct. 2025 ??00:18, jordi.palet--- via RPD >>>>> a ?crit?: >>>>> >>>>> Hi Caleb, >>>>> >>>>> The proposals that I refer: >>>>> 1) Already reached consensus. >>>>> 2) Already were sent to the board with the relevant reports. >>>>> >>>>> So from that perspective, with ?basically administrative? I >>>>> mean that there is not ?a lot of other? work to be done in the >>>>> proposals. Of course, the board should make sure that the >>>>> proposals aren?t against the company, but the legal >>>>> implications, operational feasibility, alignment with the >>>>> bylaws, etc., was already done because all this is part of the >>>>> analysis impact that was prepared *before* declaring >>>>> consensus. This is just the way the PDP works, so we aren?t >>>>> changing anything. >>>>> >>>>> Saludos, >>>>> Jordi >>>>> >>>>> @jordipalet >>>>> >>>>> >>>>>> El 8 oct 2025, a las 18:07, Caleb Ogundele >>>>>> escribi?: >>>>>> >>>>>> Hi Jordi and All, >>>>>> >>>>>> I'm happy this list is?becoming more active, and it is a good >>>>>> thing. >>>>>> Responding to @Jordi, I must respectfully differ with Jordi >>>>>> on point one. While I share the desire to see pending >>>>>> proposals move forward, I don't believe board ratification >>>>>> should be characterized as "basically an administrative task >>>>>> that should not take too much time." >>>>>> >>>>>> Board ratification is a critical governance checkpoint where >>>>>> proposals are reviewed for legal implications, operational >>>>>> feasibility, and alignment with AFRINIC's mission and bylaws. >>>>>> Given that we're emerging from three years of limited >>>>>> functionality as?a community, I believe the Community and the >>>>>> Board deserve adequate time to properly review and ratify >>>>>> proposals, especially those that may have significant >>>>>> operational or financial implications for AFRINIC and its >>>>>> members. Times have changed in the last three years and >>>>>> community members have different views on certain policies. >>>>>> Rushing this process could lead to oversights that create >>>>>> problems down the line. Quality should take precedence over >>>>>> speed. >>>>>> >>>>>> *Caleb Ogundele* >>>>>> /Speaking for myself as a community member >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> / >>>>>> >>>>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD >>>>>> wrote: >>>>>> >>>>>> HI Seun, all, >>>>>> >>>>>> Fully agree with your view. I will add 2 more points: >>>>>> >>>>>> 1) There are several policy proposals that reached >>>>>> consensus and are ?paused? just waiting for the board >>>>>> ratification. I understand the board will be very busy, >>>>>> but the ratification is basically an administrative task >>>>>> that should not take too much time. So please, consider >>>>>> doing so ASAP, so the implementation can also be >>>>>> initiated, as I think in some cases it may take long time. >>>>>> >>>>>> >>>>>> 2) Some of use may need to plan ahead, and buy our >>>>>> flights as early as possible (too close to the meeting >>>>>> become extremely expensive when traveling from abroad) >>>>>> for the next PPM, so it will be good to announce firm >>>>>> dates and location as soon as possible. >>>>>> >>>>>> Those that have policy proposals still under discussion >>>>>> really need to have a status summary and specially >>>>>> understand if the actual co-chairs will continue as >>>>>> suggested, so we can restart our work and encourage >>>>>> discussions in the community. >>>>>> >>>>>> Finally, I don?t think we need a ?complete modernization >>>>>> of the policy manual?, but instead concentrate in review >>>>>> the existing discussion and decide if we need to focus on >>>>>> any new topic at the time being. >>>>>> >>>>>> Tks! >>>>>> >>>>>> Saludos, >>>>>> Jordi >>>>>> >>>>>> @jordipalet >>>>>> >>>>>> >>>>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji >>>>>>> escribi?: >>>>>>> >>>>>>> Hello Ben, RPD >>>>>>> >>>>>>> It's good that this discussion is starting up. I don't >>>>>>> think anything revolutionary with the rpd needs to >>>>>>> happen from the board level at this time. The rpd itself >>>>>>> should evolve through policies and while the board >>>>>>> indeed has the ability to write a policy when required >>>>>>> and in certain?circumstances i do think that it isn't >>>>>>> necessary at this time. I would suggest the following: >>>>>>> >>>>>>> 1. Current Co-Chairs continue in their role towards the >>>>>>> next Public Policy Meeting (PPM) and they should >>>>>>> coordinate on the things Sami mentioned with regards to >>>>>>> authors representing their proposal and new proposals as >>>>>>> applicable. >>>>>>> >>>>>>> 2. We usually hold 2 PPMs every year 1 during the AIS >>>>>>> and another at the second AFRINIC pubic meeting in the >>>>>>> year, it will be good for the Board to provide the rpd >>>>>>> with some information on how soon that can happen. >>>>>>> >>>>>>> 3. With the recent board election, staff does have >>>>>>> significant experience on conducting credible and >>>>>>> verifiable election. The Board should leverage on that >>>>>>> to organise election of Co-Chairs at the next ppm inline >>>>>>> with the CPM. The 2 seats should be filled in a >>>>>>> staggered manner >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> ---- >>>>>>> Sent from my mobile >>>>>>> kindly excuse typos >>>>>>> >>>>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via >>>>>>> RPD, wrote: >>>>>>> >>>>>>> Sami, >>>>>>> Thanks for your mail and we appreciate your >>>>>>> contributions to PWDG to date and are happy to see >>>>>>> you are keen to start it up again. I am replying as >>>>>>> a community member, though I am also a board member >>>>>>> of AfriNIC. >>>>>>> >>>>>>> I feel that as we restart the PWDG process, what is >>>>>>> absolutely key is that we get *much more* diversity >>>>>>> in that process. My question back to you is to ask, >>>>>>> how do we invigorate the process to involve many >>>>>>> more key experts in the digital economy of Africa? >>>>>>> >>>>>>> Kind regards >>>>>>> Ben >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board >>>>>>>> wrote: >>>>>>>> >>>>>>>> ? >>>>>>>> *Dear PDWG Community,* >>>>>>>> * >>>>>>>> * >>>>>>>> I hope this message finds you well. >>>>>>>> >>>>>>>> I would like to take this opportunity to >>>>>>>> congratulate you all on the successful election of >>>>>>>> the AFRINIC Board and the resumption of its proper >>>>>>>> functioning. This milestone marks an important step >>>>>>>> toward restoring stability, trust, and continuity >>>>>>>> in AFRINIC?s role as the Regional Internet Registry >>>>>>>> for Africa. With governance now back on track, it >>>>>>>> is the right moment to resume the Policy >>>>>>>> Development Process (PDP) and address the policy >>>>>>>> gaps that have accumulated during the past three >>>>>>>> years of interruption. >>>>>>>> >>>>>>>> As you are aware, over the past three years AFRINIC >>>>>>>> has gone through a period of limited functionality, >>>>>>>> and the Policy Development Process (PDP) has been >>>>>>>> effectively paused. During this time, the global >>>>>>>> Internet number community has continued to evolve, >>>>>>>> with significant policy updates taking place across >>>>>>>> the other RIRs. This has created a widening gap >>>>>>>> between AFRINIC?s Consolidated Policy Manual (CPM) >>>>>>>> and those of our sister RIRs. >>>>>>>> >>>>>>>> In order to restore the momentum of policy >>>>>>>> development in our region and to ensure that >>>>>>>> AFRINIC?s policy environment remains relevant, >>>>>>>> consistent, and globally aligned, I would like to >>>>>>>> highlight the following areas where action is needed: >>>>>>>> >>>>>>>> *Previous PDWG Co-Chairs* >>>>>>>> While their terms have now ended, we request that >>>>>>>> the most recent PDWG Co-Chairs prepare a short >>>>>>>> report summarizing the last set of policy proposals >>>>>>>> that were under discussion before the process >>>>>>>> stalled. We further encourage the original authors >>>>>>>> of those drafts to resubmit them for renewed >>>>>>>> community review, or alternatively, invite any >>>>>>>> community member to take initiative to re-submit >>>>>>>> and champion them. >>>>>>>> >>>>>>>> *AFRINIC Board* >>>>>>>> We call on the Board to formally publish a >>>>>>>> community call for modernizing the AFRINIC Policy >>>>>>>> Manual. This would include identifying and >>>>>>>> prioritizing areas where policy alignment with >>>>>>>> other RIRs is needed (e.g., IPv4 transfer >>>>>>>> frameworks, IPv6 allocation criteria, RPKI >>>>>>>> adoption, Whois/privacy reforms, and >>>>>>>> membership/resource governance models). Such a call >>>>>>>> would help set a clear direction and provide >>>>>>>> legitimacy to the process of catching up with >>>>>>>> global best practices. >>>>>>>> >>>>>>>> *PDWG Community* >>>>>>>> Most importantly, we urge all community members to >>>>>>>> actively re-engage in the PDP by discussing any >>>>>>>> submitted proposals, providing constructive >>>>>>>> feedback, and enriching the drafts with insights >>>>>>>> drawn from operational experience. The strength of >>>>>>>> AFRINIC?s PDP has always been rooted in the >>>>>>>> diversity and expertise of its community, and your >>>>>>>> participation will be crucial in shaping the future >>>>>>>> of Internet number resource management in our region. >>>>>>>> >>>>>>>> This is a collective responsibility, and now is the >>>>>>>> right moment to re-energize our PDP and demonstrate >>>>>>>> the resilience of the AFRINIC community. >>>>>>>> >>>>>>>> With Regards. >>>>>>>> >>>>>>>> *Sami Salih*, PhD (ICT), PMP? >>>>>>>> Assistant Professor, Sudan University of Science >>>>>>>> and Technology >>>>>>>> Tel: (249) 122045707 >>>>>>>> _______________________________________________ >>>>>>>> Board mailing list -- board at afrinic.net >>>>>>>> To unsubscribe send an email to board-leave at afrinic.net >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>> >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> >>>>>> ********************************************** >>>>>> IPv4 is over >>>>>> Are you ready for the new Internet ? >>>>>> http://www.theipv6company.com >>>>>> The IPv6 Company >>>>>> >>>>>> This electronic message contains information which may be >>>>>> privileged or confidential. The information is intended >>>>>> to be for the exclusive use of the individual(s) named >>>>>> above and further non-explicilty authorized disclosure, >>>>>> copying, distribution or use of the contents of this >>>>>> information, even if partially, including attached files, >>>>>> is strictly prohibited and will be considered a criminal >>>>>> offense. If you are not the intended recipient be aware >>>>>> that any disclosure, copying, distribution or use of the >>>>>> contents of this information, even if partially, >>>>>> including attached files, is strictly prohibited, will be >>>>>> considered a criminal offense, so you must reply to the >>>>>> original sender to inform about this communication and >>>>>> delete it. >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Caleb Ogundele* >>>>>> Email: muyiwacaleb at gmail.com >>>>> >>>>> >>>>> ********************************************** >>>>> IPv4 is over >>>>> Are you ready for the new Internet ? >>>>> http://www.theipv6company.com >>>>> The IPv6 Company >>>>> >>>>> This electronic message contains information which may be >>>>> privileged or confidential. The information is intended to be >>>>> for the exclusive use of the individual(s) named above and >>>>> further non-explicilty authorized disclosure, copying, >>>>> distribution or use of the contents of this information, even >>>>> if partially, including attached files, is strictly prohibited >>>>> and will be considered a criminal offense. If you are not the >>>>> intended recipient be aware that any disclosure, copying, >>>>> distribution or use of the contents of this information, even >>>>> if partially, including attached files, is strictly >>>>> prohibited, will be considered a criminal offense, so you must >>>>> reply to the original sender to inform about this >>>>> communication and delete it. >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> >>> ********************************************** >>> IPv4 is over >>> Are you ready for the new Internet ? >>> http://www.theipv6company.com >>> The IPv6 Company >>> >>> This electronic message contains information which may be privileged >>> or confidential. The information is intended to be for the exclusive >>> use of the individual(s) named above and further non-explicilty >>> authorized disclosure, copying, distribution or use of the contents >>> of this information, even if partially, including attached files, is >>> strictly prohibited and will be considered a criminal offense. If >>> you are not the intended recipient be aware that any disclosure, >>> copying, distribution or use of the contents of this information, >>> even if partially, including attached files, is strictly prohibited, >>> will be considered a criminal offense, so you must reply to the >>> original sender to inform about this communication and delete it. >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged > or confidential. The information is intended to be for the exclusive > use of the individual(s) named above and further non-explicilty > authorized disclosure, copying, distribution or use of the contents of > this information, even if partially, including attached files, is > strictly prohibited and will be considered a criminal offense. If you > are not the intended recipient be aware that any disclosure, copying, > distribution or use of the contents of this information, even if > partially, including attached files, is strictly prohibited, will be > considered a criminal offense, so you must reply to the original > sender to inform about this communication and delete it. > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Fri Oct 10 12:49:34 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Fri, 10 Oct 2025 14:49:34 +0200 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <963D75E3-3E70-4FD9-BEE6-954F8288FE94@consulintel.es> References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> <7453596d-d70c-4b5f-a946-e38e5deba633@uls.co.za> <3CF6F3DC-BB61-4D1F-A2D5-46469A231364@consulintel.es> <59225eb0-d96c-4f64-b5a1-b89106e591e7@uls.co.za> <963D75E3-3E70-4FD9-BEE6-954F8288FE94@consulintel.es> Message-ID: <3c800240-4360-4123-bb5b-39a59885d3c1@uls.co.za> Hi, On 2025/10/10 14:43, jordi.palet--- via RPD wrote: > When you sign the service agreement to obtain resources in any RIR, > you accept to be bind to the policy manual which is a ?live law?, it > gets updated at any time ?and changes apply to all. Otherwise, it will > be useless to have a PDP to update the policy manual. So clearly yes > to your point 1 and 2. This is actively under dispute in court.? So clearly not so clearly :). I'm going to refrain from comment on the rest of your response, but do take note of the content. Thank you for the engagement. Kind regards, Jaco > > If there was a right to leasing (which was not the case), and policy > change to avoid that, it can be enforced, also in the other way around. > > There is not way, following the PDP, we can do a ?reassessment? of the > PDWG opinion, and you also know that it will be difficult to have > everyone agreeing. That why the decisions are based in consensus not > voting, and consensus has been already determined by the chairs. > > Delaying the decision for the ratification is a very ugly manipulation > of the process because then it means the time expires and the policies > are enforced back to the list. This will mean we can?t trust on the > new board, which will be a very bad situation. > > Regards, > Jordi > > @jordipalet > > >> El 10 oct 2025, a las 3:12, Jaco Kroon escribi?: >> >> Hi Raymond, >> >> Jordi is right in that once policies have been passed to the board >> it's not really trivial for them to push it back to the PDP, and >> Jordi is also right in that "what gives them the right?" (which is >> what I paraphrased from his writing).? That's a very valid question. >> >> I would personally rather have the board be on the side of caution, >> and send everything back to the chairs to revalidate, as new inputs >> from the last couple of years may very well result in a different >> impact assessment. >> >> I do also think that going forward we need to have a legal assessment >> on all new policies too - even if (in my made up estimation) the far >> bulk of policies will not have legal implications, however, contracts >> may be impacted by policies.? Specifically, some of the sticky points >> that came up in discussion: >> >> 1.? Can rule/policy changes be enforced retroactively? >> 2.? If a contract specifically states you're allowed to do xyz, does >> that preclude everything else, or is only what is specifically >> precluded contractually precluded? >> >> To make this even more sticky, let's say that a new policy takes away >> a right you previously had (implied or otherwise, for example, the >> topic of whether you're allowed to lease/sell/broker Afrinic IPv4 >> space, which is hotly debated with some saying you're allowed to and >> some saying you're not - I have my opinions on this but that's >> orthogonal to discussion I'm trying to have so please treat it as an >> example and not the topic), is that enforceable? >> >> What if a new policy/rule gives you a new right you didn't have >> previously? >> >> Clearly there are potentially legal implications here that can (and >> plainly has) negatively impacted the company (Afrinic).? And >> hopefully it's clear that the answers are not clear cut black and >> white, even though we'd like them to be. >> >> I think given the above a pause is in order to allow a re-assessment >> of all policies that has been submitted to board for ratification. >> >> I would also like to know if there is a list of such policies, and >> where it can be found, or if one of the staff members are possibly in >> a position to provide such a list, along with the wording impact on >> the CPM and the impact assessments that were provided. >> >> This should allow the PDWG to quickly state "we're OK with these >> proceeding, we'd like these back" etc ... assuming no one points out >> a policy issue with what I'm proposing. >> >> Kind regards, >> Jaco >> >> On 2025/10/10 10:43, Raymond Mamattah wrote: >>> Great discussions! >>> >>> My one cent is that due to the impasse we have had, which is due >>> partly to AFRINIC's own by-laws/policies, I think the Board would >>> have to look critically and with multiple checks before ratifying >>> any policy. >>> >>> I also think we should not push for a policy that's not already >>> passed to be hurriedly ratified. Ideally such policies should go >>> through "public comments" for critical checks before being passed on >>> for ratification. >>> >>> Care must be taken so we don't have a "stone-around our neck to make >>> us easily sink" again. >>> >>> Regards, >>> >>> --- >>> Raymond Mamattah >>> Accra, Ghana ?? >>> >>> On Fri, 10 Oct 2025, 08:10 Jaco Kroon, wrote: >>> >>> Hi Jordi, >>> >>> I fully agree with what you say here. >>> >>> There are however pending disputes regarding legitimacy of a >>> couple of members who could use the specific policy to sidestep >>> the issue.? The policy needs to be adjusted to ensure that only >>> members who's not only in good standing, but who is fully >>> compliant with existing policies and where there are no ongoing >>> disputes/court cases etc ... are allowed to transfer out. >>> >>> Kind regards, >>> Jaco >>> >>> On 2025/10/09 17:10, jordi.palet--- via RPD wrote: >>>> I don?t think membership status has anything to do with PDP. >>>> >>>> Ideally PDP is contributed by many members actively >>>> participating, but I think this is not the case (not only in >>>> Afrinic, also in general in other RIRs). >>>> >>>> Even if I personally disagree with the transfer policy that got >>>> consensus declared, I think it should be ratified immediately, >>>> because implementation takes many months (as experienced by >>>> other RIRs). In that period, we still have the chance to >>>> improve it, if the community believe that needs to be done. >>>> Then small implementation changes can often be done very quickly. >>>> >>>> This is the same for any policy that reached consensus, even >>>> for the complete policy manual. It is a ?live law?, the >>>> community has the chance to*always* change or improve things. >>>> What it will be useless and long time consuming is when >>>> something that reached consensus (and had a positive impact >>>> analisys) is returned to the list to re-start again the full >>>> process. Again, if something can be improved, let?s do it based >>>> on the already approved text, not from scracth. >>>> >>>> Regards, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>>> El 9 oct 2025, a las 6:42, Jaco Kroon >>>>> escribi?: >>>>> >>>>> Hi, >>>>> >>>>> That policy specifically may be one we may want to hold off >>>>> until current membership status has been sorted out first.? Or >>>>> at least the policy should be amended to compensate for what >>>>> we've learned in the last five years. >>>>> >>>>> Kind regards, >>>>> Jaco >>>>> >>>>> On 2025/10/09 02:21, Emmanuel Vitus wrote: >>>>> >>>>>> Good to see the list active again. Hopefully we can keep the >>>>>> energy focused this time and not fall back into the long >>>>>> circular debates we had in the past. >>>>>> It could help to have a simple matrix showing which proposals >>>>>> can be ratified quickly with little or no cost and which ones >>>>>> may need more time or legal review. A timeline would also be >>>>>> useful to follow progress taking into account the Board >>>>>> comments and the steps before ratification. >>>>>> The transfer policy should move forward as soon as >>>>>> possible,?my 2cents. >>>>>> Cheers! >>>>>> >>>>>> - Emmanuel >>>>>> >>>>>> Le?jeu. 9 oct. 2025 ??00:18, jordi.palet--- via RPD >>>>>> a ?crit?: >>>>>> >>>>>> Hi Caleb, >>>>>> >>>>>> The proposals that I refer: >>>>>> 1) Already reached consensus. >>>>>> 2) Already were sent to the board with the relevant reports. >>>>>> >>>>>> So from that perspective, with ?basically administrative? >>>>>> I mean that there is not ?a lot of other? work to be done >>>>>> in the proposals. Of course, the board should make sure >>>>>> that the proposals aren?t against the company, but the >>>>>> legal implications, operational feasibility, alignment >>>>>> with the bylaws, etc., was already done because all this >>>>>> is part of the analysis impact that was prepared *before* >>>>>> declaring consensus. This is just the way the PDP works, >>>>>> so we aren?t changing anything. >>>>>> >>>>>> Saludos, >>>>>> Jordi >>>>>> >>>>>> @jordipalet >>>>>> >>>>>> >>>>>>> El 8 oct 2025, a las 18:07, Caleb Ogundele >>>>>>> escribi?: >>>>>>> >>>>>>> Hi Jordi and All, >>>>>>> >>>>>>> I'm happy this list is?becoming more active, and it is a >>>>>>> good thing. >>>>>>> Responding to @Jordi, I must respectfully differ with >>>>>>> Jordi on point one. While I share the desire to see >>>>>>> pending proposals move forward, I don't believe board >>>>>>> ratification should be characterized as "basically an >>>>>>> administrative task that should not take too much time." >>>>>>> >>>>>>> Board ratification is a critical governance checkpoint >>>>>>> where proposals are reviewed for legal implications, >>>>>>> operational feasibility, and alignment with AFRINIC's >>>>>>> mission and bylaws. Given that we're emerging from three >>>>>>> years of limited functionality as?a community, I believe >>>>>>> the Community and the Board deserve adequate time to >>>>>>> properly review and ratify proposals, especially those >>>>>>> that may have significant operational or financial >>>>>>> implications for AFRINIC and its members. Times have >>>>>>> changed in the last three years and community members >>>>>>> have different views on certain policies. Rushing this >>>>>>> process could lead to oversights that create problems >>>>>>> down the line. Quality should take precedence over speed. >>>>>>> >>>>>>> *Caleb Ogundele* >>>>>>> /Speaking for myself as a community member >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> / >>>>>>> >>>>>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD >>>>>>> wrote: >>>>>>> >>>>>>> HI Seun, all, >>>>>>> >>>>>>> Fully agree with your view. I will add 2 more points: >>>>>>> >>>>>>> 1) There are several policy proposals that reached >>>>>>> consensus and are ?paused? just waiting for the >>>>>>> board ratification. I understand the board will be >>>>>>> very busy, but the ratification is basically an >>>>>>> administrative task that should not take too much >>>>>>> time. So please, consider doing so ASAP, so the >>>>>>> implementation can also be initiated, as I think in >>>>>>> some cases it may take long time. >>>>>>> >>>>>>> >>>>>>> 2) Some of use may need to plan ahead, and buy our >>>>>>> flights as early as possible (too close to the >>>>>>> meeting become extremely expensive when traveling >>>>>>> from abroad) for the next PPM, so it will be good to >>>>>>> announce firm dates and location as soon as possible. >>>>>>> >>>>>>> Those that have policy proposals still under >>>>>>> discussion really need to have a status summary and >>>>>>> specially understand if the actual co-chairs will >>>>>>> continue as suggested, so we can restart our work >>>>>>> and encourage discussions in the community. >>>>>>> >>>>>>> Finally, I don?t think we need a ?complete >>>>>>> modernization of the policy manual?, but instead >>>>>>> concentrate in review the existing discussion and >>>>>>> decide if we need to focus on any new topic at the >>>>>>> time being. >>>>>>> >>>>>>> Tks! >>>>>>> >>>>>>> Saludos, >>>>>>> Jordi >>>>>>> >>>>>>> @jordipalet >>>>>>> >>>>>>> >>>>>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji >>>>>>>> escribi?: >>>>>>>> >>>>>>>> Hello Ben, RPD >>>>>>>> >>>>>>>> It's good that this discussion is starting up. I >>>>>>>> don't think anything revolutionary with the rpd >>>>>>>> needs to happen from the board level at this time. >>>>>>>> The rpd itself should evolve through policies and >>>>>>>> while the board indeed has the ability to write a >>>>>>>> policy when required and in certain?circumstances i >>>>>>>> do think that it isn't necessary at this time. I >>>>>>>> would suggest the following: >>>>>>>> >>>>>>>> 1. Current Co-Chairs continue in their role towards >>>>>>>> the next Public Policy Meeting (PPM) and they >>>>>>>> should coordinate on the things Sami mentioned with >>>>>>>> regards to authors representing their proposal and >>>>>>>> new proposals as applicable. >>>>>>>> >>>>>>>> 2. We usually hold 2 PPMs every year 1 during the >>>>>>>> AIS and another at the second AFRINIC pubic meeting >>>>>>>> in the year, it will be good for the Board to >>>>>>>> provide the rpd with some information on how soon >>>>>>>> that can happen. >>>>>>>> >>>>>>>> 3. With the recent board election, staff does have >>>>>>>> significant experience on conducting credible and >>>>>>>> verifiable election. The Board should leverage on >>>>>>>> that to organise election of Co-Chairs at the next >>>>>>>> ppm inline with the CPM. The 2 seats should be >>>>>>>> filled in a staggered manner >>>>>>>> >>>>>>>> Regards >>>>>>>> >>>>>>>> ---- >>>>>>>> Sent from my mobile >>>>>>>> kindly excuse typos >>>>>>>> >>>>>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC >>>>>>>> via RPD, wrote: >>>>>>>> >>>>>>>> Sami, >>>>>>>> Thanks for your mail and we appreciate your >>>>>>>> contributions to PWDG to date and are happy to >>>>>>>> see you are keen to start it up again. I am >>>>>>>> replying as a community member, though I am >>>>>>>> also a board member of AfriNIC. >>>>>>>> >>>>>>>> I feel that as we restart the PWDG process, >>>>>>>> what is absolutely key is that we get *much >>>>>>>> more* diversity in that process. My question >>>>>>>> back to you is to ask, how do we invigorate the >>>>>>>> process to involve many more key experts in the >>>>>>>> digital economy of Africa? >>>>>>>> >>>>>>>> Kind regards >>>>>>>> Ben >>>>>>>> >>>>>>>> Sent from my iPhone >>>>>>>> >>>>>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> ? >>>>>>>>> *Dear PDWG Community,* >>>>>>>>> * >>>>>>>>> * >>>>>>>>> I hope this message finds you well. >>>>>>>>> >>>>>>>>> I would like to take this opportunity to >>>>>>>>> congratulate you all on the successful >>>>>>>>> election of the AFRINIC Board and the >>>>>>>>> resumption of its proper functioning. This >>>>>>>>> milestone marks an important step toward >>>>>>>>> restoring stability, trust, and continuity in >>>>>>>>> AFRINIC?s role as the Regional Internet >>>>>>>>> Registry for Africa. With governance now back >>>>>>>>> on track, it is the right moment to resume the >>>>>>>>> Policy Development Process (PDP) and address >>>>>>>>> the policy gaps that have accumulated during >>>>>>>>> the past three years of interruption. >>>>>>>>> >>>>>>>>> As you are aware, over the past three years >>>>>>>>> AFRINIC has gone through a period of limited >>>>>>>>> functionality, and the Policy Development >>>>>>>>> Process (PDP) has been effectively paused. >>>>>>>>> During this time, the global Internet number >>>>>>>>> community has continued to evolve, with >>>>>>>>> significant policy updates taking place across >>>>>>>>> the other RIRs. This has created a widening >>>>>>>>> gap between AFRINIC?s Consolidated Policy >>>>>>>>> Manual (CPM) and those of our sister RIRs. >>>>>>>>> >>>>>>>>> In order to restore the momentum of policy >>>>>>>>> development in our region and to ensure that >>>>>>>>> AFRINIC?s policy environment remains relevant, >>>>>>>>> consistent, and globally aligned, I would like >>>>>>>>> to highlight the following areas where action >>>>>>>>> is needed: >>>>>>>>> >>>>>>>>> *Previous PDWG Co-Chairs* >>>>>>>>> While their terms have now ended, we request >>>>>>>>> that the most recent PDWG Co-Chairs prepare a >>>>>>>>> short report summarizing the last set of >>>>>>>>> policy proposals that were under discussion >>>>>>>>> before the process stalled. We further >>>>>>>>> encourage the original authors of those drafts >>>>>>>>> to resubmit them for renewed community review, >>>>>>>>> or alternatively, invite any community member >>>>>>>>> to take initiative to re-submit and champion them. >>>>>>>>> >>>>>>>>> *AFRINIC Board* >>>>>>>>> We call on the Board to formally publish a >>>>>>>>> community call for modernizing the AFRINIC >>>>>>>>> Policy Manual. This would include identifying >>>>>>>>> and prioritizing areas where policy alignment >>>>>>>>> with other RIRs is needed (e.g., IPv4 transfer >>>>>>>>> frameworks, IPv6 allocation criteria, RPKI >>>>>>>>> adoption, Whois/privacy reforms, and >>>>>>>>> membership/resource governance models). Such a >>>>>>>>> call would help set a clear direction and >>>>>>>>> provide legitimacy to the process of catching >>>>>>>>> up with global best practices. >>>>>>>>> >>>>>>>>> *PDWG Community* >>>>>>>>> Most importantly, we urge all community >>>>>>>>> members to actively re-engage in the PDP by >>>>>>>>> discussing any submitted proposals, providing >>>>>>>>> constructive feedback, and enriching the >>>>>>>>> drafts with insights drawn from operational >>>>>>>>> experience. The strength of AFRINIC?s PDP has >>>>>>>>> always been rooted in the diversity and >>>>>>>>> expertise of its community, and your >>>>>>>>> participation will be crucial in shaping the >>>>>>>>> future of Internet number resource management >>>>>>>>> in our region. >>>>>>>>> >>>>>>>>> This is a collective responsibility, and now >>>>>>>>> is the right moment to re-energize our PDP and >>>>>>>>> demonstrate the resilience of the AFRINIC >>>>>>>>> community. >>>>>>>>> >>>>>>>>> With Regards. >>>>>>>>> >>>>>>>>> *Sami Salih*, PhD (ICT), PMP? >>>>>>>>> Assistant Professor, Sudan University of >>>>>>>>> Science and Technology >>>>>>>>> Tel: (249) 122045707 >>>>>>>>> _______________________________________________ >>>>>>>>> Board mailing list -- board at afrinic.net >>>>>>>>> To unsubscribe send an email to >>>>>>>>> board-leave at afrinic.net >>>>>>>> _______________________________________________ >>>>>>>> RPD mailing list >>>>>>>> RPD at afrinic.net >>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> RPD mailing list >>>>>>>> RPD at afrinic.net >>>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>> >>>>>>> >>>>>>> ********************************************** >>>>>>> IPv4 is over >>>>>>> Are you ready for the new Internet ? >>>>>>> http://www.theipv6company.com >>>>>>> The IPv6 Company >>>>>>> >>>>>>> This electronic message contains information which >>>>>>> may be privileged or confidential. The information >>>>>>> is intended to be for the exclusive use of the >>>>>>> individual(s) named above and further non-explicilty >>>>>>> authorized disclosure, copying, distribution or use >>>>>>> of the contents of this information, even if >>>>>>> partially, including attached files, is strictly >>>>>>> prohibited and will be considered a criminal >>>>>>> offense. If you are not the intended recipient be >>>>>>> aware that any disclosure, copying, distribution or >>>>>>> use of the contents of this information, even if >>>>>>> partially, including attached files, is strictly >>>>>>> prohibited, will be considered a criminal offense, >>>>>>> so you must reply to the original sender to inform >>>>>>> about this communication and delete it. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Caleb Ogundele* >>>>>>> Email: muyiwacaleb at gmail.com >>>>>> >>>>>> >>>>>> ********************************************** >>>>>> IPv4 is over >>>>>> Are you ready for the new Internet ? >>>>>> http://www.theipv6company.com >>>>>> The IPv6 Company >>>>>> >>>>>> This electronic message contains information which may be >>>>>> privileged or confidential. The information is intended >>>>>> to be for the exclusive use of the individual(s) named >>>>>> above and further non-explicilty authorized disclosure, >>>>>> copying, distribution or use of the contents of this >>>>>> information, even if partially, including attached files, >>>>>> is strictly prohibited and will be considered a criminal >>>>>> offense. If you are not the intended recipient be aware >>>>>> that any disclosure, copying, distribution or use of the >>>>>> contents of this information, even if partially, >>>>>> including attached files, is strictly prohibited, will be >>>>>> considered a criminal offense, so you must reply to the >>>>>> original sender to inform about this communication and >>>>>> delete it. >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> ********************************************** >>>> IPv4 is over >>>> Are you ready for the new Internet ? >>>> http://www.theipv6company.com >>>> The IPv6 Company >>>> >>>> This electronic message contains information which may be >>>> privileged or confidential. The information is intended to be >>>> for the exclusive use of the individual(s) named above and >>>> further non-explicilty authorized disclosure, copying, >>>> distribution or use of the contents of this information, even >>>> if partially, including attached files, is strictly prohibited >>>> and will be considered a criminal offense. If you are not the >>>> intended recipient be aware that any disclosure, copying, >>>> distribution or use of the contents of this information, even >>>> if partially, including attached files, is strictly prohibited, >>>> will be considered a criminal offense, so you must reply to the >>>> original sender to inform about this communication and delete it. >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged > or confidential. The information is intended to be for the exclusive > use of the individual(s) named above and further non-explicilty > authorized disclosure, copying, distribution or use of the contents of > this information, even if partially, including attached files, is > strictly prohibited and will be considered a criminal offense. If you > are not the intended recipient be aware that any disclosure, copying, > distribution or use of the contents of this information, even if > partially, including attached files, is strictly prohibited, will be > considered a criminal offense, so you must reply to the original > sender to inform about this communication and delete it. > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Thu Oct 9 22:04:56 2025 From: owen at delong.com (Owen DeLong) Date: Thu, 9 Oct 2025 15:04:56 -0700 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From omo.oaiya at wacren.net Sun Oct 12 10:26:15 2025 From: omo.oaiya at wacren.net (Omo Oaiya) Date: Sun, 12 Oct 2025 11:26:15 +0100 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: Message-ID: <5DF5ED45-A4B2-4DEB-B279-A7C045495500@wacren.net> It?s great to see discussion back on the list, a good sign that the community spirit is still strong. I agree with Owen. What really matters is that the feedback loop stays open, clear, and timely. On Ben?s point, participation will grow if we make the PDP more inclusive and relevant. We should bring in people from IXPs, NRENs, academia, civil society, and sectors shaping Africa?s digital economy. Linking policy work to that wider digital transformation agenda will draw new energy and perspectives. Let?s keep it going. Best, Omo > On 9 Oct 2025, at 23:04, Owen DeLong via RPD wrote: > > Like it or not, Jordi, the board has a fiduciary responsibility that is not shared by the PDWG and co-chairs. They must do due diligence reviewing proposals for consequences to the business, potential legal ramifications, etc. and if they find something amiss the must remand the proposal to the PDWG with an explanation of what they find problematic and ideally suggested possible fixes. > > Owen > > >> On Oct 9, 2025, at 08:03, jordi.palet--- via RPD wrote: >> >> ?Yes Sami, you got it. >> >> However, also we must say that returning policies that reached consensus and had a positive impact analysis to the list will be like the board telling the authors and the rest of the community ?we don?t mind the time you had spend on this, we don?t trust you, you?re irrelevant because we are the board, etc.?, so I don?t think it is a good way to start if we want to trust the new board members. As I just said, the board can only ?not-ratify? a policy when it is going to harm the company. >> >> Hopefully they already followed the PDP discussions and they are able to be informed by the staff and read the reports that are prepared when a policy proposal reach consensus. >> >> Regards, >> Jordi >> >> @jordipalet >> >> >>> El 8 oct 2025, a las 22:29, Sami Salih escribi?: >>> >>> Thank you all for the active participation, I truly missed this spirit of debate. >>> >>> If I may echo and translate Jourdi?s point: we need the Board to either ratify the proposal or return it to the list. Keeping it pending for an unnecessary period is not helping anyone. >>> >>> In addition, we need the Board?s decision regarding the co-chair, as it is difficult to move forward without clear leadership and facilitation for the group. >>> >>> I?m very glad to see things getting back on track ? >>> >>> Best regards, >>> Sami >>> >>> Sent from Outlook for Android >>> From: Caleb Ogundele >>> Sent: Thursday, October 9, 2025 3:48:53 AM >>> To: jordi.palet at consulintel.es >>> Cc: rpd >>> Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual >>> >>> Hi Jordi, >>> >>> Just a reminder that we have both been co-authors of a PDP process, which means you know I have an understanding of the PDP process, as you do. On the other hand, you're absolutely right that impact analysis is conducted before consensus is declared, and I appreciate you explaining that context at least to those who might be joining the PDP process recently. The board also has the right to send it back to the community for review. >>> >>> However, I still believe we should be cautious about characterizing board ratification as primarily administrative, even for proposals that reached consensus before the pause. Here's why: >>> >>> Context has changed significantly: These proposals reached consensus before the three-year interruption. The operational landscape, AFRINIC's financial position, staffing capabilities, and even other RIRs have evolved during this period. The Board has a fiduciary responsibility to reassess whether the original impact analyses still hold true given current circumstances. >>> >>> New Board composition: With the recent election, we have Board members who weren't part of the original discussions around these proposals. They need adequate time to review the proposals, understand the consensus process that led to them, and ask questions if needed. Expecting quick rubber-stamping doesn't serve good governance. >>> >>> Rebuilding trust requires thoroughness: After three years of limited functionality, the community needs to see that governance processes are working properly - not just quickly. A measured, transparent review by the Board (even if it takes a bit longer) will build more confidence than rushing through ratifications. >>> >>> Just to be clear, I absolutely agree that these proposals should move forward; however, technology has evolved in the last three years, and other RIRs have implemented new policies that may affect other issues. However, I share your concern about the timeline. >>> >>> Best regards, >>> >>> Caleb Ogundele >>> Speaking for myself as a community member >>> >>> >>> On Wed, Oct 8, 2025 at 7:24?PM jordi.palet--- via RPD > wrote: >>> Hi Caleb, >>> >>> The proposals that I refer: >>> 1) Already reached consensus. >>> 2) Already were sent to the board with the relevant reports. >>> >>> So from that perspective, with ?basically administrative? I mean that there is not ?a lot of other? work to be done in the proposals. Of course, the board should make sure that the proposals aren?t against the company, but the legal implications, operational feasibility, alignment with the bylaws, etc., was already done because all this is part of the analysis impact that was prepared *before* declaring consensus. This is just the way the PDP works, so we aren?t changing anything. >>> >>> Saludos, >>> Jordi >>> >>> @jordipalet >>> >>> >>>> El 8 oct 2025, a las 18:07, Caleb Ogundele > escribi?: >>>> >>>> Hi Jordi and All, >>>> >>>> I'm happy this list is becoming more active, and it is a good thing. >>>> Responding to @Jordi, I must respectfully differ with Jordi on point one. While I share the desire to see pending proposals move forward, I don't believe board ratification should be characterized as "basically an administrative task that should not take too much time." >>>> Board ratification is a critical governance checkpoint where proposals are reviewed for legal implications, operational feasibility, and alignment with AFRINIC's mission and bylaws. Given that we're emerging from three years of limited functionality as a community, I believe the Community and the Board deserve adequate time to properly review and ratify proposals, especially those that may have significant operational or financial implications for AFRINIC and its members. Times have changed in the last three years and community members have different views on certain policies. Rushing this process could lead to oversights that create problems down the line. Quality should take precedence over speed. >>>> >>>> Caleb Ogundele >>>> Speaking for myself as a community member >>>> >>>> >>>> >>>> >>>> >>>> On Wed, Oct 8, 2025 at 6:34?PM jordi.palet--- via RPD > wrote: >>>> HI Seun, all, >>>> >>>> Fully agree with your view. I will add 2 more points: >>>> >>>> 1) There are several policy proposals that reached consensus and are ?paused? just waiting for the board ratification. I understand the board will be very busy, but the ratification is basically an administrative task that should not take too much time. So please, consider doing so ASAP, so the implementation can also be initiated, as I think in some cases it may take long time. >>>> >>>> >>>> 2) Some of use may need to plan ahead, and buy our flights as early as possible (too close to the meeting become extremely expensive when traveling from abroad) for the next PPM, so it will be good to announce firm dates and location as soon as possible. >>>> >>>> Those that have policy proposals still under discussion really need to have a status summary and specially understand if the actual co-chairs will continue as suggested, so we can restart our work and encourage discussions in the community. >>>> >>>> Finally, I don?t think we need a ?complete modernization of the policy manual?, but instead concentrate in review the existing discussion and decide if we need to focus on any new topic at the time being. >>>> >>>> Tks! >>>> >>>> Saludos, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>>> El 8 oct 2025, a las 17:02, Seun Ojedeji > escribi?: >>>>> >>>>> Hello Ben, RPD >>>>> >>>>> It's good that this discussion is starting up. I don't think anything revolutionary with the rpd needs to happen from the board level at this time. The rpd itself should evolve through policies and while the board indeed has the ability to write a policy when required and in certain circumstances i do think that it isn't necessary at this time. I would suggest the following: >>>>> >>>>> 1. Current Co-Chairs continue in their role towards the next Public Policy Meeting (PPM) and they should coordinate on the things Sami mentioned with regards to authors representing their proposal and new proposals as applicable. >>>>> >>>>> 2. We usually hold 2 PPMs every year 1 during the AIS and another at the second AFRINIC pubic meeting in the year, it will be good for the Board to provide the rpd with some information on how soon that can happen. >>>>> >>>>> 3. With the recent board election, staff does have significant experience on conducting credible and verifiable election. The Board should leverage on that to organise election of Co-Chairs at the next ppm inline with the CPM. The 2 seats should be filled in a staggered manner >>>>> >>>>> Regards >>>>> >>>>> ---- >>>>> Sent from my mobile >>>>> kindly excuse typos >>>>> >>>>> On Wed, 8 Oct 2025, 6:00?pm Ben Roberts - AfriNIC via RPD, > wrote: >>>>> Sami, >>>>> Thanks for your mail and we appreciate your contributions to PWDG to date and are happy to see you are keen to start it up again. I am replying as a community member, though I am also a board member of AfriNIC. >>>>> >>>>> I feel that as we restart the PWDG process, what is absolutely key is that we get much more diversity in that process. My question back to you is to ask, how do we invigorate the process to involve many more key experts in the digital economy of Africa? >>>>> >>>>> Kind regards >>>>> Ben >>>>> >>>>> Sent from my iPhone >>>>> >>>>>> On 6 Oct 2025, at 08:08, Sami Salih via Board > wrote: >>>>>> >>>>>> ? >>>>>> Dear PDWG Community, >>>>>> >>>>>> I hope this message finds you well. >>>>>> >>>>>> I would like to take this opportunity to congratulate you all on the successful election of the AFRINIC Board and the resumption of its proper functioning. This milestone marks an important step toward restoring stability, trust, and continuity in AFRINIC?s role as the Regional Internet Registry for Africa. With governance now back on track, it is the right moment to resume the Policy Development Process (PDP) and address the policy gaps that have accumulated during the past three years of interruption. >>>>>> >>>>>> As you are aware, over the past three years AFRINIC has gone through a period of limited functionality, and the Policy Development Process (PDP) has been effectively paused. During this time, the global Internet number community has continued to evolve, with significant policy updates taking place across the other RIRs. This has created a widening gap between AFRINIC?s Consolidated Policy Manual (CPM) and those of our sister RIRs. >>>>>> >>>>>> In order to restore the momentum of policy development in our region and to ensure that AFRINIC?s policy environment remains relevant, consistent, and globally aligned, I would like to highlight the following areas where action is needed: >>>>>> >>>>>> Previous PDWG Co-Chairs >>>>>> While their terms have now ended, we request that the most recent PDWG Co-Chairs prepare a short report summarizing the last set of policy proposals that were under discussion before the process stalled. We further encourage the original authors of those drafts to resubmit them for renewed community review, or alternatively, invite any community member to take initiative to re-submit and champion them. >>>>>> >>>>>> AFRINIC Board >>>>>> We call on the Board to formally publish a community call for modernizing the AFRINIC Policy Manual. This would include identifying and prioritizing areas where policy alignment with other RIRs is needed (e.g., IPv4 transfer frameworks, IPv6 allocation criteria, RPKI adoption, Whois/privacy reforms, and membership/resource governance models). Such a call would help set a clear direction and provide legitimacy to the process of catching up with global best practices. >>>>>> >>>>>> PDWG Community >>>>>> Most importantly, we urge all community members to actively re-engage in the PDP by discussing any submitted proposals, providing constructive feedback, and enriching the drafts with insights drawn from operational experience. The strength of AFRINIC?s PDP has always been rooted in the diversity and expertise of its community, and your participation will be crucial in shaping the future of Internet number resource management in our region. >>>>>> >>>>>> This is a collective responsibility, and now is the right moment to re-energize our PDP and demonstrate the resilience of the AFRINIC community. >>>>>> >>>>>> With Regards. >>>>>> >>>>>> Sami Salih, PhD (ICT), PMP? >>>>>> Assistant Professor, Sudan University of Science and Technology >>>>>> Tel: (249) 122045707 >>>>>> _______________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Sun Oct 12 18:49:38 2025 From: noah at neo.co.tz (Noah) Date: Sun, 12 Oct 2025 21:49:38 +0300 Subject: [rpd] Call for Action: - Resource Transfer Policy In-Reply-To: References: <9D47EF82-240B-4200-A402-5E411D21685E@afrinic.net> <764AC659-0267-45FC-A5D7-6C696145726E@consulintel.es> Message-ID: On Thu, 9 Oct 2025, 3:25?am jordi.palet--- via RPD, wrote: > Hi Caleb, > > The proposals that I refer: > 1) Already reached consensus. > 2) Already were sent to the board with the relevant reports. > One such proposal is the Resource Transfer Policy - linked below. https://afrinic.net/policy/proposals/2020-gen-006-d3 Draft 3 of the proposal obtained and reached consensus after years of discussion by the Internet Community. The co-chairs sent draft 3 of the propos to the board for ratification. The Courts did not grant the Injunction. There was a case by Cloud Innovation Limited against the proposal in form of an Injunction. https://afrinic.net/court-cases Case number 5 2021 Jun 25 Cloud Innovation Ltd vs AFRINIC SC/COM/MOT/000382/2021 Application for injunction ? ref Resource Transfer Policy (Not granted) The policy is pending immediate ratification. Noah > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Sun Oct 12 22:39:49 2025 From: ben.roberts at afrinic.net (Ben Roberts - AfriNIC) Date: Mon, 13 Oct 2025 01:39:49 +0300 Subject: [rpd] Call for Action: - Resource Transfer Policy In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From comms at afrinic.net Mon Oct 13 05:54:08 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Mon, 13 Oct 2025 09:54:08 +0400 Subject: [rpd] =?utf-8?q?Communiqu=C3=A9_from_the_AFRINIC_Board_of_Directo?= =?utf-8?q?rs_and_the_Receiver?= Message-ID: [Joint Statement from the AFRINIC Board of Directors and the Receiver] Dear AFRINIC Resource Members and Internet Community, The AFRINIC Board of Directors and the Receiver, Mr. Gowtamsingh Dabee, wish to inform all AFRINIC Resource Members and the AFRINIC Internet Community that both parties are working in close collaboration to fulfil AFRINIC?s obligations to its members, employees, and stakeholders, as well as to the broader regional and international Internet community. On 08 October 2025, the Receiver filed his report titled ?Application for Termination of Receivership? before the Supreme Court (Bankruptcy Division) of Mauritius, thereby initiating the process for his formal release. A decision of the Honourable Court is currently awaited. The Board extends its sincere appreciation to Mr. Dabee for his dedication and invaluable efforts in guiding AFRINIC to this significant stage, one where a Board of Directors is now in place. The Board notes that certain legal proceedings initiated against AFRINIC, both prior to and following the recent elections, remain ongoing. The Board will work towards a quick resolution of these matters, thereby enabling AFRINIC to resume full and normal operations. Until the Receiver?s formal discharge by the Honourable Court, Mr. Dabee has graciously agreed to continue supporting AFRINIC in implementing the necessary steps following the appointment of Directors. AFRINIC Staff and Leadership Transition The Board and the Receiver wish to commend the AFRINIC staff for their dedication, professionalism, and resilience in maintaining operations under unprecedented circumstances, including functioning without a Chief Executive Officer for nearly three years. We reaffirm our commitment to supporting, protecting, and recognising staff for their service. Both the Board and the Receiver are working closely to identify short- and long-term solutions for the recruitment of a new Chief Executive Officer at the earliest possible opportunity. Membership and IP Resources The Board is currently reviewing matters related to IP resource allocations and the rights of all Resource Members who have joined AFRINIC since June 2022. This matter, being the subject of ongoing court proceedings, is receiving careful legal consideration. The Board also reiterates its commitment to the integrity of AFRINIC?s WHOIS database and the protection of members? IP resource rights. Board Committees Recognising the substantial volume of work ahead, the following sub-committees of the Board have been constituted to strengthen governance and assist in its functions: ? Finance Committee ? chaired by Ms. Carla Sanderson ? Audit Committee ? chaired by Dr. Fiona Asonga ? Remuneration Committee ? chaired by Mr. Laurent Ntumba ? Legal Committee ? chaired by Mr. Ben Roberts These committees will review the work that has been paused since 2022 and realign AFRINIC?s governance as the organisation enters 2026. The newly constituted Legal Committee has been mandated to take stock of all ongoing legal cases involving AFRINIC, with the objective of optimising legal resources and ensuring that AFRINIC maintains an appropriate and coherent legal strategy moving forward. Appointment of Auditor and Financial Reports In accordance with AFRINIC?s statutory obligations, the Receiver has appointed Forvis Mazars, a licensed firm by the Mauritius Financial Reporting Council (FRC), as external auditor to conduct financial audits for the years 2022, 2023, and 2024. This appointment was made under exceptional circumstances, in the absence of an Annual General Members? Meeting (AGMM), to respond to stakeholder requests for audited financial statements and to ensure the continuity of AFRINIC?s operations. Preliminary assessments indicate that significant work remains to be completed. The audit exercises are ongoing and are expected to be finalised shortly. The audit partners are currently reviewing the audit files. The Board is reviewing the financial reports for 2022?2024, which will be published online once approved. A summary of the audited reports will also be made available on the AFRINIC website to ensure transparency and accountability. Special General Members? Meeting The Board recognises the need to convene a Special General Members? Meeting (SGMM) to present the company?s 2021 audited financial statements. Members will recall that during the last AGMM in 2022, the resolution to adopt the Audited Financial Statement for the year ended 31 December 2021 was not approved, and consequently, the Companies Act requires that where ?the financial statements are not approved at the annual meeting, they shall be presented at a further special meeting called by the Board?. The Board is reviewing the appropriate course of action and will shortly revert to the membership with the proposed way forward. Legal Matters and Investigations The Legal Committee is reviewing information concerning the alleged use of fraudulent Power of Attorney (PoA) or ?Power to Vote? documents during the aborted June 2025 elections. These documents are reportedly with the relevant investigatory authorities in Mauritius. The Board will update members once preliminary investigations are completed, and acomprehensive update will follow upon the Committee?s review of all ongoing litigations and related legal matters. Policy Development and Community Representation The Board recognises the importance of relaunching the Policy Development Process (PDP) as a core mechanism of the bottom-up governance model and as a requirement under the ICP-2 framework. In this regard, the Board will soon reopen PDP discussions, issue a call for Policy Development Working Group (PDWG) Co-Chairs, and invite the submission or resubmission of policy proposals for community review. A key prerequisite will be to ensure that all community mailing lists maintain an atmosphere of civility and constructive engagement. Additionally, the Board is taking steps to reconstitute key community structures, including the African representatives to the NRO NC / ASO AC, to ensure full and balanced regional representation in the global Internet ecosystem. Governance Committee The Board has taken note that the mandate of the members of the previous Governance Committee (GovCom) has ended. The Board is reviewing its composition and mandate to ensure alignment with AFRINIC?s current governance priorities. Suggestions received from members have been noted, and further updates on the reconstitution of the Committee will be communicated in due course. Bylaws Review and Institutional Reform In light of the circumstances that led to AFRINIC?s recent challenges, the Board recognises the urgent need for a comprehensive review of the Bylaws and institutional reform to strengthen governance and ensure AFRINIC?s long-term sustainability. A call for volunteers to participate in this critical reform exercise will be issued in due course. The Board invites all Resource Members and community stakeholders to actively participate in rebuilding AFRINIC. Conclusion The AFRINIC Board of Directors and the Receiver reaffirm their joint commitment to rebuilding trust, restoring stability, and re-establishing AFRINIC?s reputation and legitimacy as a key actor in the global Internet ecosystem. We will continue to engage with multistakeholder organisations that have supported AFRINIC through these challenging years, including ICANN, ISOC, the NRO, local authorities, and other regional and international partners, as collaboration remains vital to the strength of the Regional Internet Registry system. The Board is also committed to deepening engagement with its membership, consistent with the bottom-up model. To this end, regular Board-Community Engagement Sessions will be introduced, both online and in person, to listen to members? views and gather feedback on the way forward. AFRINIC Board of Directors and the Receiver -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahilefranc at gmail.com Mon Oct 13 06:08:40 2025 From: ahilefranc at gmail.com (Ahile shagba francis) Date: Mon, 13 Oct 2025 07:08:40 +0100 Subject: [rpd] RPD Digest, Vol 214, Issue 29 In-Reply-To: References: Message-ID: RE: Communique C?est une action louable de la part du Conseil. On Mon, 13 Oct 2025 at 6:54?AM, wrote: > Send RPD mailing list submissions to > rpd at afrinic.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.afrinic.net/mailman/listinfo/rpd > or, via email, send a message with subject or body 'help' to > rpd-request at afrinic.net > > You can reach the person managing the list at > rpd-owner at afrinic.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of RPD digest..." > > > Today's Topics: > > 1. Re: Call for Action: - Resource Transfer Policy (Noah) > 2. Re: Call for Action: - Resource Transfer Policy > (Ben Roberts - AfriNIC) > 3. Communiqu? from the AFRINIC Board of Directors and the > Receiver (AFRINIC Communication) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 12 Oct 2025 21:49:38 +0300 > From: Noah > To: rpd > Subject: Re: [rpd] Call for Action: - Resource Transfer Policy > Message-ID: > BC8fqiz6g3-kyrcrM+ug at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Thu, 9 Oct 2025, 3:25?am jordi.palet--- via RPD, > wrote: > > > Hi Caleb, > > > > The proposals that I refer: > > 1) Already reached consensus. > > 2) Already were sent to the board with the relevant reports. > > > > > One such proposal is the Resource Transfer Policy - linked below. > > https://afrinic.net/policy/proposals/2020-gen-006-d3 > > Draft 3 of the proposal obtained and reached consensus after years of > discussion by the Internet Community. > > The co-chairs sent draft 3 of the propos to the board for ratification. The > Courts did not grant the Injunction. > > There was a case by Cloud Innovation Limited against the proposal in form > of an Injunction. > > https://afrinic.net/court-cases > Case number 5 > 2021 Jun 25 Cloud Innovation Ltd vs AFRINIC > SC/COM/MOT/000382/2021 Application for injunction ? ref Resource Transfer > Policy > (Not granted) > > The policy is pending immediate ratification. > > Noah > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20251012/a0d37b80/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Mon, 13 Oct 2025 01:39:49 +0300 > From: Ben Roberts - AfriNIC > To: Noah > Cc: rpd > Subject: Re: [rpd] Call for Action: - Resource Transfer Policy > Message-ID: > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20251013/6cdcf938/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Mon, 13 Oct 2025 09:54:08 +0400 > From: AFRINIC Communication > To: rpd > Subject: [rpd] Communiqu? from the AFRINIC Board of Directors and the > Receiver > Message-ID: > Content-Type: text/plain; charset="utf-8" > > [Joint Statement from the AFRINIC Board of Directors and the Receiver] > > Dear AFRINIC Resource Members and Internet Community, > > The AFRINIC Board of Directors and the Receiver, Mr. Gowtamsingh Dabee, > wish to inform all AFRINIC Resource Members and the AFRINIC Internet > Community that both parties are working in close collaboration to fulfil > AFRINIC?s obligations to its members, employees, and stakeholders, as well > as to the broader regional and international Internet community. > > On 08 October 2025, the Receiver filed his report titled ?Application for > Termination of Receivership? before the Supreme Court (Bankruptcy Division) > of Mauritius, thereby initiating the process for his formal release. A > decision of the Honourable Court is currently awaited. > > The Board extends its sincere appreciation to Mr. Dabee for his dedication > and invaluable efforts in guiding AFRINIC to this significant stage, one > where a Board of Directors is now in place. > > The Board notes that certain legal proceedings initiated against AFRINIC, > both prior to and following the recent elections, remain ongoing. The Board > will work towards a quick resolution of these matters, thereby enabling > AFRINIC to resume full and normal operations. Until the Receiver?s formal > discharge by the Honourable Court, Mr. Dabee has graciously agreed to > continue supporting AFRINIC in implementing the necessary steps following > the appointment of Directors. > > AFRINIC Staff and Leadership Transition > The Board and the Receiver wish to commend the AFRINIC staff for their > dedication, professionalism, and resilience in maintaining operations under > unprecedented circumstances, including functioning without a Chief > Executive Officer for nearly three years. > We reaffirm our commitment to supporting, protecting, and recognising > staff for their service. Both the Board and the Receiver are working > closely to identify short- and long-term solutions for the recruitment of a > new Chief Executive Officer at the earliest possible opportunity. > > Membership and IP Resources > The Board is currently reviewing matters related to IP resource > allocations and the rights of all Resource Members who have joined AFRINIC > since June 2022. This matter, being the subject of ongoing court > proceedings, is receiving careful legal consideration. > The Board also reiterates its commitment to the integrity of AFRINIC?s > WHOIS database and the protection of members? IP resource rights. > > Board Committees > Recognising the substantial volume of work ahead, the following > sub-committees of the Board have been constituted to strengthen governance > and assist in its functions: > ? Finance Committee ? chaired by Ms. Carla Sanderson > ? Audit Committee ? chaired by Dr. Fiona Asonga > ? Remuneration Committee ? chaired by Mr. Laurent Ntumba > ? Legal Committee ? chaired by Mr. Ben Roberts > These committees will review the work that has been paused since 2022 and > realign AFRINIC?s governance as the organisation enters 2026. The newly > constituted Legal Committee has been mandated to take stock of all ongoing > legal cases involving AFRINIC, > with the objective of optimising legal resources and ensuring that AFRINIC > maintains an appropriate and coherent legal strategy moving forward. > > Appointment of Auditor and Financial Reports > In accordance with AFRINIC?s statutory obligations, the Receiver has > appointed Forvis Mazars, a licensed firm by the Mauritius Financial > Reporting Council (FRC), as external auditor to conduct financial audits > for the years 2022, 2023, and 2024. > This appointment was made under exceptional circumstances, in the absence > of an Annual General Members? Meeting (AGMM), to respond to stakeholder > requests for audited financial statements and to ensure the continuity of > AFRINIC?s operations. > Preliminary assessments indicate that significant work remains to be > completed. The audit exercises are ongoing and are expected to be finalised > shortly. The audit partners are currently reviewing the audit files. > The Board is reviewing the financial reports for 2022?2024, which will be > published online once approved. A summary of the audited reports will also > be made available on the AFRINIC website to ensure transparency and > accountability. > > Special General Members? Meeting > The Board recognises the need to convene a Special General Members? > Meeting (SGMM) to present the company?s 2021 audited financial statements. > Members will recall that during the last AGMM in 2022, the resolution to > adopt the Audited Financial Statement for the year ended 31 December 2021 > was not approved, and consequently, the Companies Act requires that where > ?the financial statements are not > approved at the annual meeting, they shall be presented at a further > special meeting called > by the Board?. > The Board is reviewing the appropriate course of action and will shortly > revert to the membership with the proposed way forward. > > Legal Matters and Investigations > The Legal Committee is reviewing information concerning the alleged use of > fraudulent Power of Attorney (PoA) or ?Power to Vote? documents during the > aborted June 2025 elections. > These documents are reportedly with the relevant investigatory authorities > in Mauritius. The Board will update members once preliminary investigations > are completed, and acomprehensive update will follow upon the Committee?s > review of all ongoing litigations and > related legal matters. > > Policy Development and Community Representation > The Board recognises the importance of relaunching the Policy Development > Process (PDP) as a core mechanism of the bottom-up governance model and as > a requirement under the ICP-2 framework. > In this regard, the Board will soon reopen PDP discussions, issue a call > for Policy Development Working Group (PDWG) Co-Chairs, and invite the > submission or resubmission of policy > proposals for community review. > A key prerequisite will be to ensure that all community mailing lists > maintain an atmosphere of civility and constructive engagement. > Additionally, the Board is taking steps to reconstitute key community > structures, including the African representatives to the NRO NC / ASO AC, > to ensure full and balanced regional representation in the global Internet > ecosystem. > > Governance Committee > The Board has taken note that the mandate of the members of the previous > Governance Committee (GovCom) has ended. The Board is reviewing its > composition and mandate to ensure alignment with AFRINIC?s current > governance priorities. > Suggestions received from members have been noted, and further updates on > the reconstitution of the Committee will be communicated in due course. > > Bylaws Review and Institutional Reform > In light of the circumstances that led to AFRINIC?s recent challenges, the > Board recognises the urgent need for a comprehensive review of the Bylaws > and institutional reform to strengthen governance and ensure AFRINIC?s > long-term sustainability. > A call for volunteers to participate in this critical reform exercise will > be issued in due course. The Board invites all Resource Members and > community stakeholders to actively participate in rebuilding AFRINIC. > > Conclusion > The AFRINIC Board of Directors and the Receiver reaffirm their joint > commitment to rebuilding > trust, restoring stability, and re-establishing AFRINIC?s reputation and > legitimacy as a key actor > in the global Internet ecosystem. > We will continue to engage with multistakeholder organisations that have > supported AFRINIC through these challenging years, including ICANN, ISOC, > the NRO, local authorities, and other regional and international partners, > as collaboration remains vital to the strength of the Regional Internet > Registry system. > The Board is also committed to deepening engagement with its membership, > consistent with the bottom-up model. To this end, regular Board-Community > Engagement Sessions will be introduced, both online and in person, to > listen to members? views and gather feedback on the way forward. > > AFRINIC Board of Directors and the Receiver > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://lists.afrinic.net/pipermail/rpd/attachments/20251013/9cb4b2de/attachment.html > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > ------------------------------ > > End of RPD Digest, Vol 214, Issue 29 > ************************************ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at iptrading.com Mon Oct 13 13:59:13 2025 From: mike at iptrading.com (Mike Burns) Date: Mon, 13 Oct 2025 09:59:13 -0400 Subject: [rpd] Call for Action: - Resource Transfer Policy In-Reply-To: References: Message-ID: <020301dc3c49$8e69f4a0$ab3ddde0$@iptrading.com> ?Only Legacy resources and resources transferred in from other regions will be transferable out of the AFRINIC service region.? ?Must be the right holder of the resources to be transferred with no disputes.? Some important parts of the transfer policy pending ratification. I hope the new board will ratify this and not return it to the PDP. Regards, Mike From: Ben Roberts - AfriNIC via RPD Sent: Sunday, October 12, 2025 6:40 PM To: Noah Cc: rpd Subject: Re: [rpd] Call for Action: - Resource Transfer Policy Noah, Well noted. Cheers Ben Sent from my iPhone On 12 Oct 2025, at 21:52, Noah > wrote: ? On Thu, 9 Oct 2025, 3:25?am jordi.palet--- via RPD, > wrote: Hi Caleb, The proposals that I refer: 1) Already reached consensus. 2) Already were sent to the board with the relevant reports. One such proposal is the Resource Transfer Policy - linked below. https://afrinic.net/policy/proposals/2020-gen-006-d3 Draft 3 of the proposal obtained and reached consensus after years of discussion by the Internet Community. The co-chairs sent draft 3 of the propos to the board for ratification. The Courts did not grant the Injunction. There was a case by Cloud Innovation Limited against the proposal in form of an Injunction. https://afrinic.net/court-cases Case number 5 2021 Jun 25 Cloud Innovation Ltd vs AFRINIC SC/COM/MOT/000382/2021 Application for injunction ? ref Resource Transfer Policy (Not granted) The policy is pending immediate ratification. Noah _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Mon Oct 13 14:43:07 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Mon, 13 Oct 2025 17:43:07 +0300 Subject: [rpd] Questions about IP Allocation rate Message-ID: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: From fhfrediani at gmail.com Mon Oct 13 15:54:00 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Mon, 13 Oct 2025 12:54:00 -0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: Hi Allocating resources for Future Use is commonly important when you can't predict things in long term and think it was a good decision taken in the past. Same thing for Critical Infrastructure Resources reservation that most RIRs have. They have a clear reason to exist and be treated as such. If we, as a Community, are going to discuss allocation of remaining reserved resources I firmly believe this should be done with enough time to analyze the current IPv4 exhaustion, demand in the region and how it can benefit most organization in Africa. A /12 may be a lot but don't be surprised how fast that can go. Therefore we should have as basis some fundamental restrictions in order to make sure these resources go to those willing to build Internet Infrastructure AND (this and is important) that currently have no chances to get much IPv4 space. I am talking about newcomers. In order for them to exist and start building something they need some minimal space, get at cruising speed and be more independent from there. Those who already have some allocations are more likely to have revenue to transfer further blocks as required. The current /22 limitation well tested in other RIRs and provides a reasonable minimal amount of IPv4 to start with. This favors the emergence of a greater number of organizations that build Internet Infrastructure in the region, which is always positive for greater competitiveness and innovation in this ecosystem. Best regards Fernando Frediani On 10/13/2025 11:43 AM, Andrew Alston wrote: > Hi All, > > I was wondering if there were updated statistics for the amount of > space allocated in the last 3 years.? In addition to this information > regarding exactly how much free space is still available in the IPv4 > unallocated pool (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a > /12 worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if > we still, after 14 years, have not been able to articulate a clear > reason for such a large reservation, I think it's time we look at > most, if not all, of that /12 back into the main unallocated pool that > can be allocated for African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious > use or even potential theft. > > Thanks > > Andrew > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd From admin at megamore.ng Mon Oct 13 15:54:37 2025 From: admin at megamore.ng (Amin Dayekh) Date: Mon, 13 Oct 2025 16:54:37 +0100 Subject: [rpd] Call for Action: - Resource Transfer Policy Message-ID: hi, I find no reasonable reasons to hold the process as long as it reached consensus. In the case referenced, apparently there was an attempt to stop this policy via courts and it failed, delays or return of the policy will be misunderstood. No matter how other RIR policies have evolved, policy remains a policy and consensus remains consensus; it is like outdating the 10 commandments because they are very old or the society has evolved. As long as the Policies don't break any rule of law, or go against any law, what are we cautious about? A community can create any process and policy as long as it doesn't go against any law. - Consensus - Announced on 14/01/2022 | Ratification Report sent to the Board by PDWG Chairs - 14/01/2022 ------------------------------------------- From: Noah Date: Sun, 12 Oct 2025, 9:49?pm Subject: Re: [rpd] Call for Action: - Resource Transfer Policy To: rpd Cc: On Thu, 9 Oct 2025, 3:25?am jordi.palet--- via RPD, wrote: > Hi Caleb, > > The proposals that I refer: > 1) Already reached consensus. > 2) Already were sent to the board with the relevant reports. > One such proposal is the Resource Transfer Policy - linked below. https://afrinic.net/policy/proposals/2020-gen-006-d3 Draft 3 of the proposal obtained and reached consensus after years of discussion by the Internet Community. The co-chairs sent draft 3 of the propos to the board for ratification. The Courts did not grant the Injunction. There was a case by Cloud Innovation Limited against the proposal in form of an Injunction. https://afrinic.net/court-cases Case number 5 2021 Jun 25 Cloud Innovation Ltd vs AFRINIC SC/COM/MOT/000382/2021 Application for injunction ? ref Resource Transfer Policy (Not granted) The policy is pending immediate ratification. Noah *Amin Dayekh* *CTO* *MegaMore Wireless Broadband* 9 Zango Road, Gate B Dakata, Kano State. www.megamorebroadband.com m: +2347065525271 t: +2348152525222 *customer Care*: 08077770470 e: admin at megamorebroadband.com [image: facebook icon] [image: linkedin icon] [image: instagram icon] [image: banner] **************************************************************************************** This email and any attachment (s) transmitted with it are confidential. They may also be privileged or otherwise protected by law. They are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email by error, please notify the sender immediately by e-mail and delete this e-mail from your system. You are also notified that disclosing, copying, distributing, or taking any action in relation to its contents is strictly prohibited and unlawful. By reading the message and opening any attachment, the recipient accepts full responsibility for taking protective and remedial action about viruses and other defects. **************************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Mon Oct 13 16:59:37 2025 From: noah at neo.co.tz (Noah) Date: Mon, 13 Oct 2025 19:59:37 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: 54 African States are taking public services online. Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. Each of the 54 African states need address space indepedent of LIR space in each sovereign state. These are not ideas that actors in the private sector care about or think about. Cheers, *.**/noah* On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, wrote: > Hi All, > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > Thanks > > Andrew > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Mon Oct 13 17:33:45 2025 From: ben.roberts at afrinic.net (Ben Roberts - AfriNIC) Date: Mon, 13 Oct 2025 20:33:45 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: <774DB039-D838-4C02-8CF6-D7BED5C1D2BA@afrinic.net> An HTML attachment was scrubbed... URL: From noah at neo.co.tz Mon Oct 13 19:25:03 2025 From: noah at neo.co.tz (Noah) Date: Mon, 13 Oct 2025 22:25:03 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <774DB039-D838-4C02-8CF6-D7BED5C1D2BA@afrinic.net> References: <774DB039-D838-4C02-8CF6-D7BED5C1D2BA@afrinic.net> Message-ID: Ben There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. Cheers, *.**/noah* On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, wrote: > I think The DPI systems are normally run by state owned digital agency > entities which are already mostly LIRs having some space. It is not quite > as you describe being state owned LIRs that have sovereign owned IPs that > are independent of LIRs.. > > > > Sent from my iPhone > > On 13 Oct 2025, at 20:01, Noah wrote: > > ? > 54 African States are taking public services online. > > Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. > DPI is critical. The private sector will tap into that infrastructure. Its > here now. > > Each of the 54 African states need address space indepedent of LIR space > in each sovereign state. > > These are not ideas that actors in the private sector care about or think > about. > > Cheers, > *.**/noah* > > > On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, wrote: > >> Hi All, >> >> I was wondering if there were updated statistics for the amount of space >> allocated in the last 3 years. In addition to this information regarding >> exactly how much free space is still available in the IPv4 unallocated pool >> (excluding reservations) >> >> I ask this because depending on the allocation rate - we may wish to >> consider revising the soft-landing policy that currently reserves a /12 >> worth of ipv4 space for "future uses, as yet unforeseen". >> >> I point out that the soft landing policy was ratified in 2011, and if we >> still, after 14 years, have not been able to articulate a clear reason for >> such a large reservation, I think it's time we look at most, if not all, of >> that /12 back into the main unallocated pool that can be allocated for >> African resource holders that actually need it. >> >> Amongst other reasons, sitting with unallocated, unannounced, reserved >> space like this leaves the space vulnerable to hijacking and malicious use >> or even potential theft. >> >> Thanks >> >> Andrew >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Tue Oct 14 02:41:08 2025 From: ben.roberts at afrinic.net (Ben Roberts - AfriNIC) Date: Tue, 14 Oct 2025 05:41:08 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From madhvi at afrinic.net Tue Oct 14 08:01:19 2025 From: madhvi at afrinic.net (Madhvi Gokool) Date: Tue, 14 Oct 2025 12:01:19 +0400 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> Dear Sir AFRINIC publishes statistics here - https://stats.afrinic.net The graph titled ?Distribution of IPv4 (/24) per year? on the page Statistics Portal can be referenced for yearly distribution, In addition, The ?Filter by date Range? can be used to get granular statistics for the IPv4 allocations. We also wish to inform you that while the page is accessible on Firefox and Safari browsers, we have noticed an erratic behaviour when accessed via Chrome browser. We are investigating this erratic behaviour at the moment. Kind Regards Madhvi Gokool AFRINIC Policy Liaison On 13/10/2025 18:43, Andrew Alston wrote: > Hi All, > > I was wondering if there were updated statistics for the amount of > space allocated in the last 3 years.? In addition to this information > regarding exactly how much free space is still available in the IPv4 > unallocated pool (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a > /12 worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if > we still, after 14 years, have not been able to articulate a clear > reason for such a large reservation, I think it's time we look at > most, if not all, of that /12 back into the main unallocated pool that > can be allocated for African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious > use or even potential theft. > > Thanks > > Andrew > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Tue Oct 14 08:21:27 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Tue, 14 Oct 2025 08:21:27 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 08:43:55 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 01:43:55 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 08:46:57 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 01:46:57 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> Message-ID: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen > On Oct 14, 2025, at 01:22, Hendrik Visage wrote: > > ? Question: > > Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? > > ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. > > Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" > > --- > Hendrik Visage > Instant messaging: https://t.me/hvisage > > >> On 13 Oct 2025, at 16:43, Andrew Alston wrote: >> >> Hi All, >> >> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >> >> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >> >> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >> >> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >> >> Thanks >> >> Andrew >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Tue Oct 14 09:04:21 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Tue, 14 Oct 2025 11:04:21 +0200 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> Message-ID: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet > El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: > > Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. > > Owen > > >> On Oct 14, 2025, at 01:22, Hendrik Visage wrote: >> >> ? Question: >> >> Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? >> >> ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. >> >> Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" >> >> --- >> Hendrik Visage >> Instant messaging: https://t.me/hvisage >> >> >>> On 13 Oct 2025, at 16:43, Andrew Alston wrote: >>> >>> Hi All, >>> >>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>> >>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>> >>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>> >>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>> >>> Thanks >>> >>> Andrew >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> --- >> >> Hendrik Visage >> >> hvisage at hevis.co.za >> >> >> HeViS.Co Systems Pty Ltd >> >> https://www.envisage.co.za >> >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 09:10:14 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 12:10:14 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: Hi Ben Yes lets get us get that data from Afrinic. It would be interesting to know how many African Govt have Internet Resources or which govt entities have internet resources in each country. Cheers, *.**/noah* On Tue, 14 Oct 2025, 5:41?am Ben Roberts - AfriNIC, wrote: > Ok. What we probably need is to have IP allocation statistics by African > country. We can ask Afrinic for this to be complied. From that you can work > out how many IP addresses a country has per capita of population. Our > policy setting needs to be guided by data and research, not rumour. > > According to this website, Eritrea has just over 5000 IP addresses. > https://lite.ip2location.com/eritrea-ip-address-ranges This is on the > extreme low side for a country of nearly 4 million population. Seychelles > on the other hand with population under 150,000 has multiple tens of IP > addresses (allocated to Seychelles registered companies) per capita. > > Countries that have very low uptake of IP addresses will likely be mostly > ones where regulators have not opened up the space to grant new ISP > licences, my example of Eritrea has only one AS number for instance. Whilst > AfrNIC can hold back some space for countries that forgot to build their > digital economies?, the regulators in these countries need to be engaged to > tell them ?it?s now or never?. > > > > Sent from my iPhone > > On 13 Oct 2025, at 22:25, Noah wrote: > > ? > Ben > > There is critical structural challenge in the continents digital landscape > and you more than anyone knows this very well that we also suffer from > uneven maturity of Digital Public Infrastructure and Government Networks > (GovNet), which directly impacts the equitable deployment of essential > digital services across majority of countries across our continent. > > Look we are talking about numbering infrastructure that would support > services like e-government, digital IDs, and public/private data exchanges, > while aligning with AFRINIC's exhaustion-phase policies. > > We can not shy away from these reality or pretend that there is lack of > foresight from actors at Afrinic and the community at large. > > Its a known fact that many of our African governments lack operational > GovNets and strategic reservations of IPv4 address space from AFRINIC could > serve as a targeted incentive to bridge these gaps. > > > > Cheers, > *.**/noah* > > > On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < > ben.roberts at afrinic.net> wrote: > >> I think The DPI systems are normally run by state owned digital agency >> entities which are already mostly LIRs having some space. It is not quite >> as you describe being state owned LIRs that have sovereign owned IPs that >> are independent of LIRs.. >> >> >> >> Sent from my iPhone >> >> On 13 Oct 2025, at 20:01, Noah wrote: >> >> ? >> 54 African States are taking public services online. >> >> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >> thing. DPI is critical. The private sector will tap into that >> infrastructure. Its here now. >> >> Each of the 54 African states need address space indepedent of LIR space >> in each sovereign state. >> >> These are not ideas that actors in the private sector care about or think >> about. >> >> Cheers, >> *.**/noah* >> >> >> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >> wrote: >> >>> Hi All, >>> >>> I was wondering if there were updated statistics for the amount of space >>> allocated in the last 3 years. In addition to this information regarding >>> exactly how much free space is still available in the IPv4 unallocated pool >>> (excluding reservations) >>> >>> I ask this because depending on the allocation rate - we may wish to >>> consider revising the soft-landing policy that currently reserves a /12 >>> worth of ipv4 space for "future uses, as yet unforeseen". >>> >>> I point out that the soft landing policy was ratified in 2011, and if we >>> still, after 14 years, have not been able to articulate a clear reason for >>> such a large reservation, I think it's time we look at most, if not all, of >>> that /12 back into the main unallocated pool that can be allocated for >>> African resource holders that actually need it. >>> >>> Amongst other reasons, sitting with unallocated, unannounced, reserved >>> space like this leaves the space vulnerable to hijacking and malicious use >>> or even potential theft. >>> >>> Thanks >>> >>> Andrew >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Tue Oct 14 09:11:28 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Tue, 14 Oct 2025 12:11:28 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: <16a401dc3cea$86ca7020$945f5060$@afrinic.net> On it Noah? blog post loading! From: Noah Sent: 14 October 2025 12:10 To: Ben Roberts - AfriNIC Cc: Andrew Alston ; RPD Subject: Re: [rpd] Questions about IP Allocation rate Hi Ben Yes lets get us get that data from Afrinic. It would be interesting to know how many African Govt have Internet Resources or which govt entities have internet resources in each country. Cheers, ./noah On Tue, 14 Oct 2025, 5:41?am Ben Roberts - AfriNIC, > wrote: Ok. What we probably need is to have IP allocation statistics by African country. We can ask Afrinic for this to be complied. From that you can work out how many IP addresses a country has per capita of population. Our policy setting needs to be guided by data and research, not rumour. According to this website, Eritrea has just over 5000 IP addresses. https://lite.ip2location.com/eritrea-ip-address-ranges This is on the extreme low side for a country of nearly 4 million population. Seychelles on the other hand with population under 150,000 has multiple tens of IP addresses (allocated to Seychelles registered companies) per capita. Countries that have very low uptake of IP addresses will likely be mostly ones where regulators have not opened up the space to grant new ISP licences, my example of Eritrea has only one AS number for instance. Whilst AfrNIC can hold back some space for countries that forgot to build their digital economies?, the regulators in these countries need to be engaged to tell them ?it?s now or never?. Sent from my iPhone On 13 Oct 2025, at 22:25, Noah > wrote: ? Ben There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. Cheers, ./noah On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. Sent from my iPhone On 13 Oct 2025, at 20:01, Noah > wrote: ? 54 African States are taking public services online. Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. Each of the 54 African states need address space indepedent of LIR space in each sovereign state. These are not ideas that actors in the private sector care about or think about. Cheers, ./noah On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 09:11:01 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 12:11:01 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> References: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> Message-ID: Hi Madhvi, I'm a little confused by the stats on that page. According to the CPM AfriNIC currently reserves as a /16 for IXP space and a /12 under soft landing. This accounts for a total of 1,114,112 addresses. The stats page shows total reservations of 17509 /24s - which amounts to roughly a /10 and another /14 in reserved space. This is more than 4 times the amount of reserved space that I can account for in the CPM - so what is the rest of it and what am I missing here? Thanks Andrew On Tue, Oct 14, 2025 at 11:03?AM Madhvi Gokool via RPD wrote: > Dear Sir > > AFRINIC publishes statistics here - https://stats.afrinic.net > > The graph titled ?Distribution of IPv4 (/24) per year? on the page Statistics > Portal can be referenced for yearly > distribution, In addition, The ?Filter by date Range? can be used to get > granular statistics for the IPv4 allocations. > > We also wish to inform you that while the page is accessible on Firefox > and Safari browsers, we have noticed an erratic behaviour when accessed via > Chrome browser. We are investigating this erratic behaviour at the moment. > > Kind Regards > > Madhvi Gokool > > AFRINIC Policy Liaison > > > On 13/10/2025 18:43, Andrew Alston wrote: > > Hi All, > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > Thanks > > Andrew > > > > _______________________________________________ > RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 09:20:14 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 12:20:14 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> Message-ID: Its easier to say it would be nice to see folks deploy IPv6 until you realise ...Ooh wait a minute..Ops IPv4 transfer markets still exists. That most of internet traffic is still IPv4 powered and almost all software is writted with IPv4 in mind and lots of applications dont support IPv6. And then you also realise that In Africa unlike the Global North, the cost effective access technology does not support DHCPv6 or DS-Lite and that until recently even Windows OS let alone Android has issues with supporting CLAT on most personal handsets. Linux is not mainstream desktop OS in Africa. Most of the secondhand used PC comes preinstalled with outdated Windows OS. Cheers, *.**/noah* On Tue, 14 Oct 2025, 11:44?am Owen DeLong, wrote: > Or better yet, not reserving IPv4 could spur those governments to deploy > their govnets on IPv6 from the beginning with a clean greenfield design > leapfrogging past the legacy baggage inherent in any IPv4 based solution. > > Owen > > > On Oct 13, 2025, at 12:26, Noah wrote: > > ? > Ben > > There is critical structural challenge in the continents digital landscape > and you more than anyone knows this very well that we also suffer from > uneven maturity of Digital Public Infrastructure and Government Networks > (GovNet), which directly impacts the equitable deployment of essential > digital services across majority of countries across our continent. > > Look we are talking about numbering infrastructure that would support > services like e-government, digital IDs, and public/private data exchanges, > while aligning with AFRINIC's exhaustion-phase policies. > > We can not shy away from these reality or pretend that there is lack of > foresight from actors at Afrinic and the community at large. > > Its a known fact that many of our African governments lack operational > GovNets and strategic reservations of IPv4 address space from AFRINIC could > serve as a targeted incentive to bridge these gaps. > > > > Cheers, > *.**/noah* > > > On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < > ben.roberts at afrinic.net> wrote: > >> I think The DPI systems are normally run by state owned digital agency >> entities which are already mostly LIRs having some space. It is not quite >> as you describe being state owned LIRs that have sovereign owned IPs that >> are independent of LIRs.. >> >> >> >> Sent from my iPhone >> >> On 13 Oct 2025, at 20:01, Noah wrote: >> >> ? >> 54 African States are taking public services online. >> >> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >> thing. DPI is critical. The private sector will tap into that >> infrastructure. Its here now. >> >> Each of the 54 African states need address space indepedent of LIR space >> in each sovereign state. >> >> These are not ideas that actors in the private sector care about or think >> about. >> >> Cheers, >> *.**/noah* >> >> >> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >> wrote: >> >>> Hi All, >>> >>> I was wondering if there were updated statistics for the amount of space >>> allocated in the last 3 years. In addition to this information regarding >>> exactly how much free space is still available in the IPv4 unallocated pool >>> (excluding reservations) >>> >>> I ask this because depending on the allocation rate - we may wish to >>> consider revising the soft-landing policy that currently reserves a /12 >>> worth of ipv4 space for "future uses, as yet unforeseen". >>> >>> I point out that the soft landing policy was ratified in 2011, and if we >>> still, after 14 years, have not been able to articulate a clear reason for >>> such a large reservation, I think it's time we look at most, if not all, of >>> that /12 back into the main unallocated pool that can be allocated for >>> African resource holders that actually need it. >>> >>> Amongst other reasons, sitting with unallocated, unannounced, reserved >>> space like this leaves the space vulnerable to hijacking and malicious use >>> or even potential theft. >>> >>> Thanks >>> >>> Andrew >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 09:26:05 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 12:26:05 +0300 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> Message-ID: And to add on Jordi point, we also know that have atleast /24 at bare minimum or a /22 can come in handly during IPv6 transition especially when the need for native v6 on users side requires an NAT64 and DNS64 boxes along them path especially the Gateways facing the legacy Internet. Cheers, *.**/noah* On Tue, 14 Oct 2025, 12:15?pm jordi.palet--- via RPD, wrote: > Agree, however, we know very well that a small IPv4 pool (may be a /24 for > each BGP PoP), is needed for interconnection with IPv4 Internet, as there > may be still some old apps that require it. > > Regards, > Jordi > > @jordipalet > > > El 14 oct 2025, a las 10:46, Owen DeLong via RPD > escribi?: > > Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and > the efforts to keep it from running out are actually counterproductive to > progress in the African digital economy. > > Owen > > > On Oct 14, 2025, at 01:22, Hendrik Visage wrote: > > ? Question: > > Shouldn?t we rather consider pushing IPv6 deployment assistance across > Africa? ie. let the rest of the IPv4 go ASAP without much resistance > instead of making this a begging/pleading/fighting game? > > ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 > roll outs, ?cause they don?t have any left, and looking at AfriNIC services > countries, we are still have an abundance of IPv4, so IPv6 percentage roll > outs are very low, and rathe we should be pushing to mirror the IPv6 > percentage rollout and usage rather than fighting over the few remaining > IPv4s if we want to grow digital rollouts. > > Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven > a complete IPv6 rollout can you get anymore IPv4" > > --- > Hendrik Visage > Instant messaging: https://t.me/hvisage > > > On 13 Oct 2025, at 16:43, Andrew Alston wrote: > > Hi All, > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > Thanks > > Andrew > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 09:35:30 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 12:35:30 +0300 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> Message-ID: On Tue, 14 Oct 2025, 11:31?am Hendrik Visage, wrote: > Question: > > Shouldn?t we rather consider pushing IPv6 deployment assistance across > Africa? > ie. let the rest of the IPv4 go ASAP without much resistance. > Let it go where? > ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 > roll outs, ?cause they don?t have any left, > Yes true but the operate dual-stack networks. Have the global north networks returned the IPv4 address space back to ARIN and RIPE since its legacy to them and most of them are now IPv6 ready? and looking at AfriNIC services countries, we are still have an abundance > of IPv4, > We have nothing and we never had anything. But with even the little IPv4 that we have... so IPv6 percentage roll outs are very low, > Is needed to aid with IPv6 transition... > and rathe we should be pushing to mirror the IPv6 percentage rollout and > usage rather than fighting over the few remaining IPv4s if we want to grow > digital rollouts. > Show me who in ARIN or RIPE returned their IPv4 address allocations back to the inventory after going full IPv6. > Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven > a complete IPv6 rollout can you get anymore IPv4" > Good idea for those already with IPv4 space. Let us work out a policy around the above statement which I find reasonable. > --- > Hendrik Visage > Instant messaging: https://t.me/hvisage > > > On 13 Oct 2025, at 16:43, Andrew Alston wrote: > > Hi All, > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > Thanks > > Andrew > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 09:45:17 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 12:45:17 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: I've run the data downloaded from the AfriNIC stats page to create a graph (attached) This graph shows space allocated per country and classified as "Government" or "Government Entity" and is done in terms of number of /24s. Thanks Andrew On Tue, Oct 14, 2025 at 12:10?PM Noah wrote: > Hi Ben > > Yes lets get us get that data from Afrinic. It would be interesting to > know how many African Govt have Internet Resources or which govt entities > have internet resources in each country. > > Cheers, > *.**/noah* > > > On Tue, 14 Oct 2025, 5:41?am Ben Roberts - AfriNIC, < > ben.roberts at afrinic.net> wrote: > >> Ok. What we probably need is to have IP allocation statistics by African >> country. We can ask Afrinic for this to be complied. From that you can work >> out how many IP addresses a country has per capita of population. Our >> policy setting needs to be guided by data and research, not rumour. >> >> According to this website, Eritrea has just over 5000 IP addresses. >> https://lite.ip2location.com/eritrea-ip-address-ranges This is on the >> extreme low side for a country of nearly 4 million population. Seychelles >> on the other hand with population under 150,000 has multiple tens of IP >> addresses (allocated to Seychelles registered companies) per capita. >> >> Countries that have very low uptake of IP addresses will likely be mostly >> ones where regulators have not opened up the space to grant new ISP >> licences, my example of Eritrea has only one AS number for instance. Whilst >> AfrNIC can hold back some space for countries that forgot to build their >> digital economies?, the regulators in these countries need to be engaged to >> tell them ?it?s now or never?. >> >> >> >> Sent from my iPhone >> >> On 13 Oct 2025, at 22:25, Noah wrote: >> >> ? >> Ben >> >> There is critical structural challenge in the continents digital >> landscape and you more than anyone knows this very well that we also suffer >> from uneven maturity of Digital Public Infrastructure and Government >> Networks (GovNet), which directly impacts the equitable deployment of >> essential digital services across majority of countries across our >> continent. >> >> Look we are talking about numbering infrastructure that would support >> services like e-government, digital IDs, and public/private data exchanges, >> while aligning with AFRINIC's exhaustion-phase policies. >> >> We can not shy away from these reality or pretend that there is lack of >> foresight from actors at Afrinic and the community at large. >> >> Its a known fact that many of our African governments lack operational >> GovNets and strategic reservations of IPv4 address space from AFRINIC could >> serve as a targeted incentive to bridge these gaps. >> >> >> >> Cheers, >> *.**/noah* >> >> >> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < >> ben.roberts at afrinic.net> wrote: >> >>> I think The DPI systems are normally run by state owned digital agency >>> entities which are already mostly LIRs having some space. It is not quite >>> as you describe being state owned LIRs that have sovereign owned IPs that >>> are independent of LIRs.. >>> >>> >>> >>> Sent from my iPhone >>> >>> On 13 Oct 2025, at 20:01, Noah wrote: >>> >>> ? >>> 54 African States are taking public services online. >>> >>> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >>> thing. DPI is critical. The private sector will tap into that >>> infrastructure. Its here now. >>> >>> Each of the 54 African states need address space indepedent of LIR space >>> in each sovereign state. >>> >>> These are not ideas that actors in the private sector care about or >>> think about. >>> >>> Cheers, >>> *.**/noah* >>> >>> >>> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >>> wrote: >>> >>>> Hi All, >>>> >>>> I was wondering if there were updated statistics for the amount of >>>> space allocated in the last 3 years. In addition to this information >>>> regarding exactly how much free space is still available in the IPv4 >>>> unallocated pool (excluding reservations) >>>> >>>> I ask this because depending on the allocation rate - we may wish to >>>> consider revising the soft-landing policy that currently reserves a /12 >>>> worth of ipv4 space for "future uses, as yet unforeseen". >>>> >>>> I point out that the soft landing policy was ratified in 2011, and if >>>> we still, after 14 years, have not been able to articulate a clear reason >>>> for such a large reservation, I think it's time we look at most, if not >>>> all, of that /12 back into the main unallocated pool that can be allocated >>>> for African resource holders that actually need it. >>>> >>>> Amongst other reasons, sitting with unallocated, unannounced, reserved >>>> space like this leaves the space vulnerable to hijacking and malicious use >>>> or even potential theft. >>>> >>>> Thanks >>>> >>>> Andrew >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IPv4ByCountry.png Type: image/png Size: 2085716 bytes Desc: not available URL: From ben.roberts at afrinic.net Tue Oct 14 09:48:28 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Tue, 14 Oct 2025 12:48:28 +0300 Subject: [rpd] The IPv4 Country Allocation Poverty line in Africa. In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> Message-ID: <16fa01dc3cef$b2330290$169907b0$@afrinic.net> All, Please find attached the analysed data of IPv4 allocation per capita, along with an interactive HTML map? Along with a link to my latest blog.. IPv4 Address Allocation in Africa: Are you above or Below the IP Address Poverty Line ? This analysis examines IPv4 address allocation per capita across 56 African countries using data from AfriNIC (African Network Information Centre) resource allocation statistics for 2025. The findings reveal a stark digital divide, with allocation rates varying by a factor of nearly 60,000 between the best and worst-served nations. https://www.digitaleconomy.ke/post/ipv4-address-allocation-in-africa-are-you-above-or-below-the-ip-address-poverty-line Cheers Ben From: Noah Sent: 14 October 2025 12:20 To: Owen DeLong Cc: Ben Roberts AfriNIC ; Andrew Alston ; RPD Subject: Re: [rpd] Questions about IP Allocation rate Its easier to say it would be nice to see folks deploy IPv6 until you realise ...Ooh wait a minute..Ops IPv4 transfer markets still exists. That most of internet traffic is still IPv4 powered and almost all software is writted with IPv4 in mind and lots of applications dont support IPv6. And then you also realise that In Africa unlike the Global North, the cost effective access technology does not support DHCPv6 or DS-Lite and that until recently even Windows OS let alone Android has issues with supporting CLAT on most personal handsets. Linux is not mainstream desktop OS in Africa. Most of the secondhand used PC comes preinstalled with outdated Windows OS. Cheers, ./noah On Tue, 14 Oct 2025, 11:44?am Owen DeLong, > wrote: Or better yet, not reserving IPv4 could spur those governments to deploy their govnets on IPv6 from the beginning with a clean greenfield design leapfrogging past the legacy baggage inherent in any IPv4 based solution. Owen On Oct 13, 2025, at 12:26, Noah > wrote: ? Ben There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. Cheers, ./noah On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. Sent from my iPhone On 13 Oct 2025, at 20:01, Noah > wrote: ? 54 African States are taking public services online. Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. Each of the 54 African states need address space indepedent of LIR space in each sovereign state. These are not ideas that actors in the private sector care about or think about. Cheers, ./noah On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IPV4 Count per Capita.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 14950 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 09:49:23 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 12:49:23 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: Thanks Andrew I will look at the graph on a pc as the image on the phone is not clear. I see four outstanding contries ... How many countries are those in total.? Sorry i cant see the graph clearly. Cheers, *.**/noah* On Tue, 14 Oct 2025, 12:45?pm Andrew Alston, wrote: > I've run the data downloaded from the AfriNIC stats page to create a graph > (attached) > > This graph shows space allocated per country and classified as > "Government" or "Government Entity" and is done in terms of number of /24s. > > Thanks > > Andrew > > > On Tue, Oct 14, 2025 at 12:10?PM Noah wrote: > >> Hi Ben >> >> Yes lets get us get that data from Afrinic. It would be interesting to >> know how many African Govt have Internet Resources or which govt entities >> have internet resources in each country. >> >> Cheers, >> *.**/noah* >> >> >> On Tue, 14 Oct 2025, 5:41?am Ben Roberts - AfriNIC, < >> ben.roberts at afrinic.net> wrote: >> >>> Ok. What we probably need is to have IP allocation statistics by African >>> country. We can ask Afrinic for this to be complied. From that you can work >>> out how many IP addresses a country has per capita of population. Our >>> policy setting needs to be guided by data and research, not rumour. >>> >>> According to this website, Eritrea has just over 5000 IP addresses. >>> https://lite.ip2location.com/eritrea-ip-address-ranges This is on the >>> extreme low side for a country of nearly 4 million population. Seychelles >>> on the other hand with population under 150,000 has multiple tens of IP >>> addresses (allocated to Seychelles registered companies) per capita. >>> >>> Countries that have very low uptake of IP addresses will likely be >>> mostly ones where regulators have not opened up the space to grant new ISP >>> licences, my example of Eritrea has only one AS number for instance. Whilst >>> AfrNIC can hold back some space for countries that forgot to build their >>> digital economies?, the regulators in these countries need to be engaged to >>> tell them ?it?s now or never?. >>> >>> >>> >>> Sent from my iPhone >>> >>> On 13 Oct 2025, at 22:25, Noah wrote: >>> >>> ? >>> Ben >>> >>> There is critical structural challenge in the continents digital >>> landscape and you more than anyone knows this very well that we also suffer >>> from uneven maturity of Digital Public Infrastructure and Government >>> Networks (GovNet), which directly impacts the equitable deployment of >>> essential digital services across majority of countries across our >>> continent. >>> >>> Look we are talking about numbering infrastructure that would support >>> services like e-government, digital IDs, and public/private data exchanges, >>> while aligning with AFRINIC's exhaustion-phase policies. >>> >>> We can not shy away from these reality or pretend that there is lack of >>> foresight from actors at Afrinic and the community at large. >>> >>> Its a known fact that many of our African governments lack operational >>> GovNets and strategic reservations of IPv4 address space from AFRINIC could >>> serve as a targeted incentive to bridge these gaps. >>> >>> >>> >>> Cheers, >>> *.**/noah* >>> >>> >>> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < >>> ben.roberts at afrinic.net> wrote: >>> >>>> I think The DPI systems are normally run by state owned digital agency >>>> entities which are already mostly LIRs having some space. It is not quite >>>> as you describe being state owned LIRs that have sovereign owned IPs that >>>> are independent of LIRs.. >>>> >>>> >>>> >>>> Sent from my iPhone >>>> >>>> On 13 Oct 2025, at 20:01, Noah wrote: >>>> >>>> ? >>>> 54 African States are taking public services online. >>>> >>>> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >>>> thing. DPI is critical. The private sector will tap into that >>>> infrastructure. Its here now. >>>> >>>> Each of the 54 African states need address space indepedent of LIR >>>> space in each sovereign state. >>>> >>>> These are not ideas that actors in the private sector care about or >>>> think about. >>>> >>>> Cheers, >>>> *.**/noah* >>>> >>>> >>>> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I was wondering if there were updated statistics for the amount of >>>>> space allocated in the last 3 years. In addition to this information >>>>> regarding exactly how much free space is still available in the IPv4 >>>>> unallocated pool (excluding reservations) >>>>> >>>>> I ask this because depending on the allocation rate - we may wish to >>>>> consider revising the soft-landing policy that currently reserves a /12 >>>>> worth of ipv4 space for "future uses, as yet unforeseen". >>>>> >>>>> I point out that the soft landing policy was ratified in 2011, and if >>>>> we still, after 14 years, have not been able to articulate a clear reason >>>>> for such a large reservation, I think it's time we look at most, if not >>>>> all, of that /12 back into the main unallocated pool that can be allocated >>>>> for African resource holders that actually need it. >>>>> >>>>> Amongst other reasons, sitting with unallocated, unannounced, reserved >>>>> space like this leaves the space vulnerable to hijacking and malicious use >>>>> or even potential theft. >>>>> >>>>> Thanks >>>>> >>>>> Andrew >>>>> >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 09:52:47 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 12:52:47 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: 36 Countries with a total of 2455 /24s. The 4 big countries are: South Africa (23.91%) Egypt (22.65%) Angola (15.76%) Algeria (10.43%) Thanks Andrew On Tue, Oct 14, 2025 at 12:49?PM Noah wrote: > Thanks Andrew > > I will look at the graph on a pc as the image on the phone is not clear. I > see four outstanding contries ... > > How many countries are those in total.? Sorry i cant see the graph clearly. > > Cheers, > *.**/noah* > > > On Tue, 14 Oct 2025, 12:45?pm Andrew Alston, > wrote: > >> I've run the data downloaded from the AfriNIC stats page to create a >> graph (attached) >> >> This graph shows space allocated per country and classified as >> "Government" or "Government Entity" and is done in terms of number of /24s. >> >> Thanks >> >> Andrew >> >> >> On Tue, Oct 14, 2025 at 12:10?PM Noah wrote: >> >>> Hi Ben >>> >>> Yes lets get us get that data from Afrinic. It would be interesting to >>> know how many African Govt have Internet Resources or which govt entities >>> have internet resources in each country. >>> >>> Cheers, >>> *.**/noah* >>> >>> >>> On Tue, 14 Oct 2025, 5:41?am Ben Roberts - AfriNIC, < >>> ben.roberts at afrinic.net> wrote: >>> >>>> Ok. What we probably need is to have IP allocation statistics by >>>> African country. We can ask Afrinic for this to be complied. From that you >>>> can work out how many IP addresses a country has per capita of population. >>>> Our policy setting needs to be guided by data and research, not rumour. >>>> >>>> According to this website, Eritrea has just over 5000 IP addresses. >>>> https://lite.ip2location.com/eritrea-ip-address-ranges This is on the >>>> extreme low side for a country of nearly 4 million population. Seychelles >>>> on the other hand with population under 150,000 has multiple tens of IP >>>> addresses (allocated to Seychelles registered companies) per capita. >>>> >>>> Countries that have very low uptake of IP addresses will likely be >>>> mostly ones where regulators have not opened up the space to grant new ISP >>>> licences, my example of Eritrea has only one AS number for instance. Whilst >>>> AfrNIC can hold back some space for countries that forgot to build their >>>> digital economies?, the regulators in these countries need to be engaged to >>>> tell them ?it?s now or never?. >>>> >>>> >>>> >>>> Sent from my iPhone >>>> >>>> On 13 Oct 2025, at 22:25, Noah wrote: >>>> >>>> ? >>>> Ben >>>> >>>> There is critical structural challenge in the continents digital >>>> landscape and you more than anyone knows this very well that we also suffer >>>> from uneven maturity of Digital Public Infrastructure and Government >>>> Networks (GovNet), which directly impacts the equitable deployment of >>>> essential digital services across majority of countries across our >>>> continent. >>>> >>>> Look we are talking about numbering infrastructure that would support >>>> services like e-government, digital IDs, and public/private data exchanges, >>>> while aligning with AFRINIC's exhaustion-phase policies. >>>> >>>> We can not shy away from these reality or pretend that there is lack of >>>> foresight from actors at Afrinic and the community at large. >>>> >>>> Its a known fact that many of our African governments lack operational >>>> GovNets and strategic reservations of IPv4 address space from AFRINIC could >>>> serve as a targeted incentive to bridge these gaps. >>>> >>>> >>>> >>>> Cheers, >>>> *.**/noah* >>>> >>>> >>>> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < >>>> ben.roberts at afrinic.net> wrote: >>>> >>>>> I think The DPI systems are normally run by state owned digital agency >>>>> entities which are already mostly LIRs having some space. It is not quite >>>>> as you describe being state owned LIRs that have sovereign owned IPs that >>>>> are independent of LIRs.. >>>>> >>>>> >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On 13 Oct 2025, at 20:01, Noah wrote: >>>>> >>>>> ? >>>>> 54 African States are taking public services online. >>>>> >>>>> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >>>>> thing. DPI is critical. The private sector will tap into that >>>>> infrastructure. Its here now. >>>>> >>>>> Each of the 54 African states need address space indepedent of LIR >>>>> space in each sovereign state. >>>>> >>>>> These are not ideas that actors in the private sector care about or >>>>> think about. >>>>> >>>>> Cheers, >>>>> *.**/noah* >>>>> >>>>> >>>>> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >>>>> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> I was wondering if there were updated statistics for the amount of >>>>>> space allocated in the last 3 years. In addition to this information >>>>>> regarding exactly how much free space is still available in the IPv4 >>>>>> unallocated pool (excluding reservations) >>>>>> >>>>>> I ask this because depending on the allocation rate - we may wish to >>>>>> consider revising the soft-landing policy that currently reserves a /12 >>>>>> worth of ipv4 space for "future uses, as yet unforeseen". >>>>>> >>>>>> I point out that the soft landing policy was ratified in 2011, and if >>>>>> we still, after 14 years, have not been able to articulate a clear reason >>>>>> for such a large reservation, I think it's time we look at most, if not >>>>>> all, of that /12 back into the main unallocated pool that can be allocated >>>>>> for African resource holders that actually need it. >>>>>> >>>>>> Amongst other reasons, sitting with unallocated, unannounced, >>>>>> reserved space like this leaves the space vulnerable to hijacking and >>>>>> malicious use or even potential theft. >>>>>> >>>>>> Thanks >>>>>> >>>>>> Andrew >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Tue Oct 14 09:55:07 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Tue, 14 Oct 2025 12:55:07 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> Message-ID: <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Owen, Will that not exclude many of their their citizens from accessing digital services? From: Owen DeLong Sent: 14 October 2025 11:44 To: Noah Cc: Ben Roberts AfriNIC ; Andrew Alston ; RPD Subject: Re: [rpd] Questions about IP Allocation rate Or better yet, not reserving IPv4 could spur those governments to deploy their govnets on IPv6 from the beginning with a clean greenfield design leapfrogging past the legacy baggage inherent in any IPv4 based solution. Owen On Oct 13, 2025, at 12:26, Noah > wrote: ? Ben There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. Cheers, ./noah On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. Sent from my iPhone On 13 Oct 2025, at 20:01, Noah > wrote: ? 54 African States are taking public services online. Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. Each of the 54 African states need address space indepedent of LIR space in each sovereign state. These are not ideas that actors in the private sector care about or think about. Cheers, ./noah On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Tue Oct 14 09:55:43 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Tue, 14 Oct 2025 12:55:43 +0300 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> Message-ID: <173501dc3cf0$b595c020$20c14060$@afrinic.net> Hendrik, While it is important to be considering full IPv6 roll outs? We certainly cant be discounting the IPv4 exhaustion conversation. You are probably assuming that all the players are already in the game. If one is a new startup ISP or local cloud provider, is that something you can easily go about with only IPV6 resources? New entrants, whether they be commercial ISPs, enterprises, government DPI projects, are going to need to start off with some IPV4 allocations for sure. Africa?s management of the remaining V4 pool is a vital policy consideration. Kind Regards Ben From: Hendrik Visage Sent: 14 October 2025 11:21 To: RPD Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 10:01:56 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 13:01:56 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: Not Necessarily Ben. Reality is they could back end Government Networks with V6 and front the services with V4 which map to the V6 backend. This would substantially reduce the amount of IPv4 space actually needed by the governments, and provide dual-stack from the start. I have serious doubts that you will find governments in Africa requiring external access to more than 200+ unique services (which would represent a single /24 on the front end). We also need to keep in mind that many government services are now hosted behind the likes of CloudFlare - specifically for DDoS prevention mechanisms - and I'm not sure that IPv4 allocations by government entities are necessarily a good indicator of digital migration, since these services are not hosted on IPv4 space allocated to those entities. The same applies to services hosted in any of the major cloud providers. Considering the front ending of these services by the DDoS filter providers and the like - the requirement for front end IPv4 per government in terms of services to the citizenship is actually relatively small (And certainly does not warrant reservations at the level they are at - which - as I pointed out in an earlier message seem to be far higher than what is actually called for in the CPM) Thanks Andrew On Tue, Oct 14, 2025 at 12:55?PM wrote: > Owen, > > Will that not exclude many of their their citizens from accessing digital > services? > > > > > > > > *From:* Owen DeLong > *Sent:* 14 October 2025 11:44 > *To:* Noah > *Cc:* Ben Roberts AfriNIC ; Andrew Alston < > aa at alstonnetworks.net>; RPD > *Subject:* Re: [rpd] Questions about IP Allocation rate > > > > Or better yet, not reserving IPv4 could spur those governments to deploy > their govnets on IPv6 from the beginning with a clean greenfield design > leapfrogging past the legacy baggage inherent in any IPv4 based solution. > > > > Owen > > > > > > On Oct 13, 2025, at 12:26, Noah wrote: > > ? > > Ben > > > > There is critical structural challenge in the continents digital landscape > and you more than anyone knows this very well that we also suffer from > uneven maturity of Digital Public Infrastructure and Government Networks > (GovNet), which directly impacts the equitable deployment of essential > digital services across majority of countries across our continent. > > > > Look we are talking about numbering infrastructure that would support > services like e-government, digital IDs, and public/private data exchanges, > while aligning with AFRINIC's exhaustion-phase policies. > > > > We can not shy away from these reality or pretend that there is lack of > foresight from actors at Afrinic and the community at large. > > > > Its a known fact that many of our African governments lack operational > GovNets and strategic reservations of IPv4 address space from AFRINIC could > serve as a targeted incentive to bridge these gaps. > > > > > > > > Cheers, > > *./noah* > > > > > > On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < > ben.roberts at afrinic.net> wrote: > > I think The DPI systems are normally run by state owned digital agency > entities which are already mostly LIRs having some space. It is not quite > as you describe being state owned LIRs that have sovereign owned IPs that > are independent of LIRs.. > > > > > > > > Sent from my iPhone > > > > On 13 Oct 2025, at 20:01, Noah wrote: > > ? > > 54 African States are taking public services online. > > > > Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. > DPI is critical. The private sector will tap into that infrastructure. Its > here now. > > > > Each of the 54 African states need address space indepedent of LIR space > in each sovereign state. > > > > These are not ideas that actors in the private sector care about or think > about. > > > > Cheers, > > *./noah* > > > > > > On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, wrote: > > Hi All, > > > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > > > Thanks > > > > Andrew > > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Tue Oct 14 10:03:15 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Tue, 14 Oct 2025 10:03:15 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> Message-ID: <0E332773-A3D7-4117-BA38-0648EC2EC784@hevis.co.za> On 14 Oct 2025, at 11:35, Noah wrote: On Tue, 14 Oct 2025, 11:31?am Hendrik Visage, > wrote: Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance. Let it go where? Issued to (new)members without the onerous requirements ? but yes, counterintuitive to the below ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, Yes true but the operate dual-stack networks. I?m seeing examples of IPv6 infrastructure examples, with IPv4 edges or IPv4aaS, so yeah, ?dual? but the eyeballs dual Have the global north networks returned the IPv4 address space back to ARIN and RIPE since its legacy to them and most of them are now IPv6 ready? It is chickens and eggs situations ;( As long as there are a ?value? to IPv4s, they?ll get TRADED not returned ;) so IPv6 percentage roll outs are very low, Is needed to aid with IPv6 transition... Yes, so change to: ?You get the tiniest IPv4, but we?ll be generous with IPv6? or we?ll just issue all IPv4 without asking, so we don?t have any IPv4 to issue? but here is a IPv6 !!? and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Show me who in ARIN or RIPE returned their IPv4 address allocations back to the inventory after going full IPv6. True, but when they return it, then somebody else will use/buy it, and? no incentive to move to IPv6 for new entrants ;( That is also why they?ll rather TRADE (or lease) it as they get something back for those IPv4s Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" Good idea for those already with IPv4 space. Let us work out a policy around the above statement which I find reasonable. :) Yes, mostly spitballing and wondering about the options. Though the quicker AfriNIC is in a position to say ?we don?t have any more IPv4s? the quicker the IPv4 fighting and policy issues will be gone? and basically all the court cases will be mood points. I?ll content (given I?m being on the receiving end of blocked resources) that the things NEW operators need from AfriNIC/RIR: 1) Working RIR w.r.t. ROA/RPKI/WHOIS/etc. 2) ASN - Without this you can?t peer!!! 3) IPv6 space - Now they have something to deploy a stable network For the needs towards IPv4, there are ?enough? floating IPv4 space, but without an ASN your network are hobbled to a single upstream? and without your own IPv6 your network deployment is? challenging - and in need of renumbering later as I need to do now. So yes, IPv4 is a ?thing? but there are enough free/etc. IPv4 space to trade/get in the open market? yes, paying somebody, but it pushed me to be a IPv6 only first network with IPv4 as an add on rather as a planned first! --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Tue Oct 14 10:16:52 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Tue, 14 Oct 2025 10:16:52 +0000 Subject: [rpd] The importance of ASN before IPv4 Re: Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <173501dc3cf0$b595c020$20c14060$@afrinic.net> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> <173501dc3cf0$b595c020$20c14060$@afrinic.net> Message-ID: Hi Ben, as a new operator, let me answer my experience: On 14 Oct 2025, at 11:55, ben.roberts at afrinic.net wrote: Hendrik, While it is important to be considering full IPv6 roll outs? We certainly cant be discounting the IPv4 exhaustion conversation. You are probably assuming that all the players are already in the game. If one is a new startup ISP or local cloud provider, is that something you can easily go about with only IPV6 resources? As a new entrant: (application entered 13 Oct 2024, AfriNIC approved allocations circa Nov ?24 with OR preventing it, PAID for the resources Feb ?25, RECEIVED resources Jun/Jul ?25) My SINGLE BIGGEST ISSUE was *not*having*an*ASN* !!! Not IPv4, not IPv6, but a lack of an ASN!! You can?t peer at IXPs, you can?t dual home, you are a *client* not an operator till you got a public ASN!! I reverted to acrobatics to get AS213481 https://lg-cpt1.as213481.net/ And THEN I could operate!! First order of business: IPv6 space (via LIR @RIPE as I was in a fortunate situation to still have RIPE based services) THAT allowed me to roll out my network and I could start deploying stuff! (I?ve presented my meshed setup and my IPv6 only experiences at ZANOG-WP the past 6 months!) IPv4: well, both my IPTs had some IPv4 space available, and several other IPv4 leasinig agents was knocking at my door and ?cold calling? me as soon my AS213481 popped up on peeringdb and CINX :D Today IPv4 is a 2nd class citizen refer to mirror.envisage.net.za it?s a IPv6 ONLY host! (IPv4 is SIIT-DC provided at the edge of my network) New entrants, whether they be commercial ISPs, enterprises, government DPI projects, are going to need to start off with some IPV4 allocations for sure. NEGATIVE REAL requirement is ASN!! The moment you get to the point that you don?t even need IPv4 on most of your routers with unnumbered interfaces, your mind set changes! yeah, old farting dinosaurs like me included (And yes, I?ve been playing on the internet since ?92 just ask Archie ;) IPv4 is dime a dozen? yes, you?ll need some for eyeballs, but with CGNAT/etc. your are making it a bigger political money thing that attracts greed and ? well? political stuff than digital enhancements! Africa?s management of the remaining V4 pool is a vital policy consideration. I?ll contest that. Kind Regards Ben From: Hendrik Visage > Sent: 14 October 2025 11:21 To: RPD > Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Tue Oct 14 10:19:13 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Tue, 14 Oct 2025 10:19:13 +0000 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> On 14 Oct 2025, at 11:55, ben.roberts--- via RPD wrote: Owen, Will that not exclude many of their their citizens from accessing digital services? 1) Get an ASN 2) deply IPv6 network 3) CGNAT / SIIT-DC / MAP-T - refer to Sky Networks?s presentations on IPv4aaS deployments Single /24 but you NEED that ASN first ! From: Owen DeLong > Sent: 14 October 2025 11:44 To: Noah > Cc: Ben Roberts AfriNIC >; Andrew Alston >; RPD > Subject: Re: [rpd] Questions about IP Allocation rate Or better yet, not reserving IPv4 could spur those governments to deploy their govnets on IPv6 from the beginning with a clean greenfield design leapfrogging past the legacy baggage inherent in any IPv4 based solution. Owen On Oct 13, 2025, at 12:26, Noah > wrote: ? Ben There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. Cheers, ./noah On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. Sent from my iPhone On 13 Oct 2025, at 20:01, Noah > wrote: ? 54 African States are taking public services online. Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. Each of the 54 African states need address space indepedent of LIR space in each sovereign state. These are not ideas that actors in the private sector care about or think about. Cheers, ./noah On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 10:22:02 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 13:22:02 +0300 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <173501dc3cf0$b595c020$20c14060$@afrinic.net> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> <173501dc3cf0$b595c020$20c14060$@afrinic.net> Message-ID: On Tue, 14 Oct 2025, 1:03?pm ben.roberts--- via RPD, wrote: > Hendrik, > > While it is important to be considering full IPv6 roll outs? We certainly > cant be discounting the IPv4 exhaustion conversation. > > You are probably assuming that all the players are already in the game. > If one is a new startup ISP or local cloud provider, is that something you > can easily go about with only IPV6 resources? New entrants, whether they > be commercial ISPs, enterprises, government DPI projects, are going to need > to start off with some IPV4 allocations for sure. Africa?s management of > the remaining V4 pool is a vital policy consideration. > +1 to the foresight Ben... Noah > > > Kind Regards > > > > Ben > > > > *From:* Hendrik Visage > *Sent:* 14 October 2025 11:21 > *To:* RPD > *Subject:* [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate > > > > Question: > > > > Shouldn?t we rather consider pushing IPv6 deployment assistance across > Africa? ie. let the rest of the IPv4 go ASAP without much resistance > instead of making this a begging/pleading/fighting game? > > > > ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 > roll outs, ?cause they don?t have any left, and looking at AfriNIC services > countries, we are still have an abundance of IPv4, so IPv6 percentage roll > outs are very low, and rathe we should be pushing to mirror the IPv6 > percentage rollout and usage rather than fighting over the few remaining > IPv4s if we want to grow digital rollouts. > > > > Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven > a complete IPv6 rollout can you get anymore IPv4" > > > > --- > Hendrik Visage > > Instant messaging: https://t.me/hvisage > > > > On 13 Oct 2025, at 16:43, Andrew Alston wrote: > > > > Hi All, > > > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > > > Thanks > > > > Andrew > > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Tue Oct 14 10:25:27 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Tue, 14 Oct 2025 13:25:27 +0300 Subject: [rpd] The importance of ASN before IPv4 Re: Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> <173501dc3cf0$b595c020$20c14060$@afrinic.net> Message-ID: <182101dc3cf4$dcfbf9a0$96f3ece0$@afrinic.net> Hendrik, Sorry to hear of your experiences of delay getting an ASN. I recently applied for one form RIPE and it came in 24 hours. This should be the benchmark of performance that AfrNIC aspires to. Kind Regards Ben From: Hendrik Visage Sent: 14 October 2025 13:17 To: ben.roberts at afrinic.net Cc: RPD Subject: The importance of ASN before IPv4 Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Hi Ben, as a new operator, let me answer my experience: On 14 Oct 2025, at 11:55, ben.roberts at afrinic.net wrote: Hendrik, While it is important to be considering full IPv6 roll outs? We certainly cant be discounting the IPv4 exhaustion conversation. You are probably assuming that all the players are already in the game. If one is a new startup ISP or local cloud provider, is that something you can easily go about with only IPV6 resources? As a new entrant: (application entered 13 Oct 2024, AfriNIC approved allocations circa Nov ?24 with OR preventing it, PAID for the resources Feb ?25, RECEIVED resources Jun/Jul ?25) My SINGLE BIGGEST ISSUE was *not*having*an*ASN* !!! Not IPv4, not IPv6, but a lack of an ASN!! You can?t peer at IXPs, you can?t dual home, you are a *client* not an operator till you got a public ASN!! I reverted to acrobatics to get AS213481 https://lg-cpt1.as213481.net/ And THEN I could operate!! First order of business: IPv6 space (via LIR @RIPE as I was in a fortunate situation to still have RIPE based services) THAT allowed me to roll out my network and I could start deploying stuff! (I?ve presented my meshed setup and my IPv6 only experiences at ZANOG-WP the past 6 months!) IPv4: well, both my IPTs had some IPv4 space available, and several other IPv4 leasinig agents was knocking at my door and ?cold calling? me as soon my AS213481 popped up on peeringdb and CINX :D Today IPv4 is a 2nd class citizen refer to mirror.envisage.net.za it?s a IPv6 ONLY host! (IPv4 is SIIT-DC provided at the edge of my network) New entrants, whether they be commercial ISPs, enterprises, government DPI projects, are going to need to start off with some IPV4 allocations for sure. NEGATIVE REAL requirement is ASN!! The moment you get to the point that you don?t even need IPv4 on most of your routers with unnumbered interfaces, your mind set changes! yeah, old farting dinosaurs like me included (And yes, I?ve been playing on the internet since ?92 just ask Archie ;) IPv4 is dime a dozen? yes, you?ll need some for eyeballs, but with CGNAT/etc. your are making it a bigger political money thing that attracts greed and ? well? political stuff than digital enhancements! Africa?s management of the remaining V4 pool is a vital policy consideration. I?ll contest that. Kind Regards Ben From: Hendrik Visage < hvisage at hevis.co.za> Sent: 14 October 2025 11:21 To: RPD < rpd at afrinic.net> Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston < aa at alstonnetworks.net> wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 10:25:44 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 13:25:44 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: On Tue, 14 Oct 2025, 12:53?pm Andrew Alston, wrote: > 36 Countries with a total of 2455 /24s. > > The 4 big countries are: > > South Africa (23.91%) > Egypt (22.65%) > Angola (15.76%) > Algeria (10.43%) > Ok we need to have a real conversation based on these stats... Let me dig up some country specific Govt data before I pause my next question. Noah > > Thanks > > Andrew > > > On Tue, Oct 14, 2025 at 12:49?PM Noah wrote: > >> Thanks Andrew >> >> I will look at the graph on a pc as the image on the phone is not clear. >> I see four outstanding contries ... >> >> How many countries are those in total.? Sorry i cant see the graph >> clearly. >> >> Cheers, >> *.**/noah* >> >> >> On Tue, 14 Oct 2025, 12:45?pm Andrew Alston, >> wrote: >> >>> I've run the data downloaded from the AfriNIC stats page to create a >>> graph (attached) >>> >>> This graph shows space allocated per country and classified as >>> "Government" or "Government Entity" and is done in terms of number of /24s. >>> >>> Thanks >>> >>> Andrew >>> >>> >>> On Tue, Oct 14, 2025 at 12:10?PM Noah wrote: >>> >>>> Hi Ben >>>> >>>> Yes lets get us get that data from Afrinic. It would be interesting to >>>> know how many African Govt have Internet Resources or which govt entities >>>> have internet resources in each country. >>>> >>>> Cheers, >>>> *.**/noah* >>>> >>>> >>>> On Tue, 14 Oct 2025, 5:41?am Ben Roberts - AfriNIC, < >>>> ben.roberts at afrinic.net> wrote: >>>> >>>>> Ok. What we probably need is to have IP allocation statistics by >>>>> African country. We can ask Afrinic for this to be complied. From that you >>>>> can work out how many IP addresses a country has per capita of population. >>>>> Our policy setting needs to be guided by data and research, not rumour. >>>>> >>>>> According to this website, Eritrea has just over 5000 IP addresses. >>>>> https://lite.ip2location.com/eritrea-ip-address-ranges This is on the >>>>> extreme low side for a country of nearly 4 million population. Seychelles >>>>> on the other hand with population under 150,000 has multiple tens of IP >>>>> addresses (allocated to Seychelles registered companies) per capita. >>>>> >>>>> Countries that have very low uptake of IP addresses will likely be >>>>> mostly ones where regulators have not opened up the space to grant new ISP >>>>> licences, my example of Eritrea has only one AS number for instance. Whilst >>>>> AfrNIC can hold back some space for countries that forgot to build their >>>>> digital economies?, the regulators in these countries need to be engaged to >>>>> tell them ?it?s now or never?. >>>>> >>>>> >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On 13 Oct 2025, at 22:25, Noah wrote: >>>>> >>>>> ? >>>>> Ben >>>>> >>>>> There is critical structural challenge in the continents digital >>>>> landscape and you more than anyone knows this very well that we also suffer >>>>> from uneven maturity of Digital Public Infrastructure and Government >>>>> Networks (GovNet), which directly impacts the equitable deployment of >>>>> essential digital services across majority of countries across our >>>>> continent. >>>>> >>>>> Look we are talking about numbering infrastructure that would support >>>>> services like e-government, digital IDs, and public/private data exchanges, >>>>> while aligning with AFRINIC's exhaustion-phase policies. >>>>> >>>>> We can not shy away from these reality or pretend that there is lack >>>>> of foresight from actors at Afrinic and the community at large. >>>>> >>>>> Its a known fact that many of our African governments lack operational >>>>> GovNets and strategic reservations of IPv4 address space from AFRINIC could >>>>> serve as a targeted incentive to bridge these gaps. >>>>> >>>>> >>>>> >>>>> Cheers, >>>>> *.**/noah* >>>>> >>>>> >>>>> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < >>>>> ben.roberts at afrinic.net> wrote: >>>>> >>>>>> I think The DPI systems are normally run by state owned digital >>>>>> agency entities which are already mostly LIRs having some space. It is not >>>>>> quite as you describe being state owned LIRs that have sovereign owned IPs >>>>>> that are independent of LIRs.. >>>>>> >>>>>> >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>> On 13 Oct 2025, at 20:01, Noah wrote: >>>>>> >>>>>> ? >>>>>> 54 African States are taking public services online. >>>>>> >>>>>> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >>>>>> thing. DPI is critical. The private sector will tap into that >>>>>> infrastructure. Its here now. >>>>>> >>>>>> Each of the 54 African states need address space indepedent of LIR >>>>>> space in each sovereign state. >>>>>> >>>>>> These are not ideas that actors in the private sector care about or >>>>>> think about. >>>>>> >>>>>> Cheers, >>>>>> *.**/noah* >>>>>> >>>>>> >>>>>> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >>>>>> wrote: >>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> I was wondering if there were updated statistics for the amount of >>>>>>> space allocated in the last 3 years. In addition to this information >>>>>>> regarding exactly how much free space is still available in the IPv4 >>>>>>> unallocated pool (excluding reservations) >>>>>>> >>>>>>> I ask this because depending on the allocation rate - we may wish to >>>>>>> consider revising the soft-landing policy that currently reserves a /12 >>>>>>> worth of ipv4 space for "future uses, as yet unforeseen". >>>>>>> >>>>>>> I point out that the soft landing policy was ratified in 2011, and >>>>>>> if we still, after 14 years, have not been able to articulate a clear >>>>>>> reason for such a large reservation, I think it's time we look at most, if >>>>>>> not all, of that /12 back into the main unallocated pool that can be >>>>>>> allocated for African resource holders that actually need it. >>>>>>> >>>>>>> Amongst other reasons, sitting with unallocated, unannounced, >>>>>>> reserved space like this leaves the space vulnerable to hijacking and >>>>>>> malicious use or even potential theft. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Andrew >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 10:34:07 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 13:34:07 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: Andrew At the back of your response to Ben... I know of a government operator that hosts an on-net CF instance but luckly, they have their own INR and dont necessary use CF IPs since CF supports BYOIP.. BYOIP means a govnet needs to have its own cocktail of v4/v6/ASN And the statistics should be able to show us how many of our own Govt who are working on DPI can actually BYOIP? Cheers, *.**/noah* On Tue, 14 Oct 2025, 1:02?pm Andrew Alston, wrote: > Not Necessarily Ben. > > Reality is they could back end Government Networks with V6 and front the > services with V4 which map to the V6 backend. > > This would substantially reduce the amount of IPv4 space actually needed > by the governments, and provide dual-stack from the start. I have serious > doubts that you will find governments in Africa requiring external access > to more than 200+ unique services (which would represent a single /24 on > the front end). > > We also need to keep in mind that many government services are now hosted > behind the likes of CloudFlare - specifically for DDoS prevention > mechanisms - and I'm not sure that IPv4 allocations by government entities > are necessarily a good indicator of digital migration, since these services > are not hosted on IPv4 space allocated to those entities. The same applies > to services hosted in any of the major cloud providers. > > Considering the front ending of these services by the DDoS filter > providers and the like - the requirement for front end IPv4 per government > in terms of services to the citizenship is actually relatively small (And > certainly does not warrant reservations at the level they are at - which - > as I pointed out in an earlier message seem to be far higher than what is > actually called for in the CPM) > > Thanks > > Andrew > > > On Tue, Oct 14, 2025 at 12:55?PM wrote: > >> Owen, >> >> Will that not exclude many of their their citizens from accessing digital >> services? >> >> >> >> >> >> >> >> *From:* Owen DeLong >> *Sent:* 14 October 2025 11:44 >> *To:* Noah >> *Cc:* Ben Roberts AfriNIC ; Andrew Alston < >> aa at alstonnetworks.net>; RPD >> *Subject:* Re: [rpd] Questions about IP Allocation rate >> >> >> >> Or better yet, not reserving IPv4 could spur those governments to deploy >> their govnets on IPv6 from the beginning with a clean greenfield design >> leapfrogging past the legacy baggage inherent in any IPv4 based solution. >> >> >> >> Owen >> >> >> >> >> >> On Oct 13, 2025, at 12:26, Noah wrote: >> >> ? >> >> Ben >> >> >> >> There is critical structural challenge in the continents digital >> landscape and you more than anyone knows this very well that we also suffer >> from uneven maturity of Digital Public Infrastructure and Government >> Networks (GovNet), which directly impacts the equitable deployment of >> essential digital services across majority of countries across our >> continent. >> >> >> >> Look we are talking about numbering infrastructure that would support >> services like e-government, digital IDs, and public/private data exchanges, >> while aligning with AFRINIC's exhaustion-phase policies. >> >> >> >> We can not shy away from these reality or pretend that there is lack of >> foresight from actors at Afrinic and the community at large. >> >> >> >> Its a known fact that many of our African governments lack operational >> GovNets and strategic reservations of IPv4 address space from AFRINIC could >> serve as a targeted incentive to bridge these gaps. >> >> >> >> >> >> >> >> Cheers, >> >> *./noah* >> >> >> >> >> >> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < >> ben.roberts at afrinic.net> wrote: >> >> I think The DPI systems are normally run by state owned digital agency >> entities which are already mostly LIRs having some space. It is not quite >> as you describe being state owned LIRs that have sovereign owned IPs that >> are independent of LIRs.. >> >> >> >> >> >> >> >> Sent from my iPhone >> >> >> >> On 13 Oct 2025, at 20:01, Noah wrote: >> >> ? >> >> 54 African States are taking public services online. >> >> >> >> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >> thing. DPI is critical. The private sector will tap into that >> infrastructure. Its here now. >> >> >> >> Each of the 54 African states need address space indepedent of LIR space >> in each sovereign state. >> >> >> >> These are not ideas that actors in the private sector care about or think >> about. >> >> >> >> Cheers, >> >> *./noah* >> >> >> >> >> >> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >> wrote: >> >> Hi All, >> >> >> >> I was wondering if there were updated statistics for the amount of space >> allocated in the last 3 years. In addition to this information regarding >> exactly how much free space is still available in the IPv4 unallocated pool >> (excluding reservations) >> >> >> >> I ask this because depending on the allocation rate - we may wish to >> consider revising the soft-landing policy that currently reserves a /12 >> worth of ipv4 space for "future uses, as yet unforeseen". >> >> >> >> I point out that the soft landing policy was ratified in 2011, and if we >> still, after 14 years, have not been able to articulate a clear reason for >> such a large reservation, I think it's time we look at most, if not all, of >> that /12 back into the main unallocated pool that can be allocated for >> African resource holders that actually need it. >> >> >> >> Amongst other reasons, sitting with unallocated, unannounced, reserved >> space like this leaves the space vulnerable to hijacking and malicious use >> or even potential theft. >> >> >> >> Thanks >> >> >> >> Andrew >> >> >> >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Tue Oct 14 10:35:48 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Tue, 14 Oct 2025 12:35:48 +0200 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> Message-ID: I don?t understand the ASN problem. There is no scarcity of those. We have done many IPv6 deployments, for Data Centers (then we use SIIT-DC), and for mobile and wired operators. In those cases the best solution is 464XLAT, which is the only transition mechanism valid in mobile networks, so if you have both mobile and wireless is non-sense to use different transition mechanisms. In both cases you need ?some? IPv4 addresses, and because you can?t route less than /24, most of the time, you will use a /24. If you have multiple PoPs for your BGP upstreams, then you may need multiple /24s. Regards, Jordi @jordipalet > El 14 oct 2025, a las 12:19, Hendrik Visage escribi?: > > > >> On 14 Oct 2025, at 11:55, ben.roberts--- via RPD wrote: >> >> Owen, >> Will that not exclude many of their their citizens from accessing digital services? > > 1) Get an ASN > 2) deply IPv6 network > 3) CGNAT / SIIT-DC / MAP-T - refer to Sky Networks?s presentations on IPv4aaS deployments > > Single /24 but you NEED that ASN first ! > > >> >> >> >> From: Owen DeLong > >> Sent: 14 October 2025 11:44 >> To: Noah > >> Cc: Ben Roberts AfriNIC >; Andrew Alston >; RPD > >> Subject: Re: [rpd] Questions about IP Allocation rate >> >> Or better yet, not reserving IPv4 could spur those governments to deploy their govnets on IPv6 from the beginning with a clean greenfield design leapfrogging past the legacy baggage inherent in any IPv4 based solution. >> >> Owen >> >> >> >>> On Oct 13, 2025, at 12:26, Noah > wrote: >>> >>> ? >>> Ben >>> >>> There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. >>> >>> Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. >>> >>> We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. >>> >>> Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. >>> >>> >>> >>> Cheers, >>> ./noah >>> >>> >>> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: >>>> I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. >>>> >>>> >>>> >>>> Sent from my iPhone >>>> >>>> >>>>> On 13 Oct 2025, at 20:01, Noah > wrote: >>>>> >>>>> ? >>>>> 54 African States are taking public services online. >>>>> >>>>> Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. >>>>> >>>>> Each of the 54 African states need address space indepedent of LIR space in each sovereign state. >>>>> >>>>> These are not ideas that actors in the private sector care about or think about. >>>>> >>>>> Cheers, >>>>> ./noah >>>>> >>>>> >>>>> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: >>>>>> Hi All, >>>>>> >>>>>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>>>>> >>>>>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>>>>> >>>>>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>>>>> >>>>>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>>>>> >>>>>> Thanks >>>>>> >>>>>> Andrew >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Tue Oct 14 10:37:55 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Tue, 14 Oct 2025 10:37:55 +0000 Subject: [rpd] The importance of ASN before IPv4 Re: Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <182101dc3cf4$dcfbf9a0$96f3ece0$@afrinic.net> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> <173501dc3cf0$b595c020$20c14060$@afrinic.net> <182101dc3cf4$dcfbf9a0$96f3ece0$@afrinic.net> Message-ID: <0FF3F9AD-448F-401D-B8B3-15F2FFAA9499@hevis.co.za> HI Ben, On 14 Oct 2025, at 12:25, ben.roberts at afrinic.net wrote: Hendrik, Sorry to hear of your experiences of delay getting an ASN. Past tense, but the experience gave me the realization: ASN is the most important thing, IPv4/IPv6 is easy to get! Perhaps even think about this process: 1) First apply for ASN gets issued a /48 ?for free? 2) Once connected and ASN visible and the /48 routed accordingly, may apply for IPv6 /32 and IPv4 /24 I recently applied for one form RIPE and it came in 24 hours. This should be the benchmark of performance that AfrNIC aspires to. The LIR sponsor model... Kind Regards Ben From: Hendrik Visage > Sent: 14 October 2025 13:17 To: ben.roberts at afrinic.net Cc: RPD > Subject: The importance of ASN before IPv4 Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Hi Ben, as a new operator, let me answer my experience: On 14 Oct 2025, at 11:55, ben.roberts at afrinic.net wrote: Hendrik, While it is important to be considering full IPv6 roll outs? We certainly cant be discounting the IPv4 exhaustion conversation. You are probably assuming that all the players are already in the game. If one is a new startup ISP or local cloud provider, is that something you can easily go about with only IPV6 resources? As a new entrant: (application entered 13 Oct 2024, AfriNIC approved allocations circa Nov ?24 with OR preventing it, PAID for the resources Feb ?25, RECEIVED resources Jun/Jul ?25) My SINGLE BIGGEST ISSUE was *not*having*an*ASN* !!! Not IPv4, not IPv6, but a lack of an ASN!! You can?t peer at IXPs, you can?t dual home, you are a *client* not an operator till you got a public ASN!! I reverted to acrobatics to get AS213481 https://lg-cpt1.as213481.net/ And THEN I could operate!! First order of business: IPv6 space (via LIR @RIPE as I was in a fortunate situation to still have RIPE based services) THAT allowed me to roll out my network and I could start deploying stuff! (I?ve presented my meshed setup and my IPv6 only experiences at ZANOG-WP the past 6 months!) IPv4: well, both my IPTs had some IPv4 space available, and several other IPv4 leasinig agents was knocking at my door and ?cold calling? me as soon my AS213481 popped up on peeringdb and CINX :D Today IPv4 is a 2nd class citizen refer to mirror.envisage.net.za it?s a IPv6 ONLY host! (IPv4 is SIIT-DC provided at the edge of my network) New entrants, whether they be commercial ISPs, enterprises, government DPI projects, are going to need to start off with some IPV4 allocations for sure. NEGATIVE REAL requirement is ASN!! The moment you get to the point that you don?t even need IPv4 on most of your routers with unnumbered interfaces, your mind set changes! yeah, old farting dinosaurs like me included (And yes, I?ve been playing on the internet since ?92 just ask Archie ;) IPv4 is dime a dozen? yes, you?ll need some for eyeballs, but with CGNAT/etc. your are making it a bigger political money thing that attracts greed and ? well? political stuff than digital enhancements! Africa?s management of the remaining V4 pool is a vital policy consideration. I?ll contest that. Kind Regards Ben From: Hendrik Visage > Sent: 14 October 2025 11:21 To: RPD > Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Tue Oct 14 10:52:08 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Tue, 14 Oct 2025 10:52:08 +0000 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> Message-ID: <67D708BA-2D6F-4349-ACE7-04960EF2B4EF@hevis.co.za> Hi Jordi, On 14 Oct 2025, at 12:35, jordi.palet--- via RPD wrote: I don?t understand the ASN problem. There is no scarcity of those. Well, during the period Oct ?24 till Jun ?25 you could NOT get a ASN from AfriNIC ! I?m not saying that ASNs are a scarcity, just, it is a REQUIREMENT for network operations on the BBI (Big Bad Internet) We have done many IPv6 deployments, for Data Centers (then we use SIIT-DC), and for mobile and wired operators. In those cases the best solution is 464XLAT, which is the only transition mechanism valid in mobile networks, so if you have both mobile and wireless is non-sense to use different transition mechanisms. In both cases you need ?some? IPv4 addresses, and because you can?t route less than /24, most of the time, you will use a /24. If you have multiple PoPs for your BGP upstreams, then you may need multiple /24s. I do agree on these points. Just that there are ?enough? IPv4 space in the open market to get going, Regards, Jordi @jordipalet El 14 oct 2025, a las 12:19, Hendrik Visage escribi?: On 14 Oct 2025, at 11:55, ben.roberts--- via RPD wrote: Owen, Will that not exclude many of their their citizens from accessing digital services? 1) Get an ASN 2) deply IPv6 network 3) CGNAT / SIIT-DC / MAP-T - refer to Sky Networks?s presentations on IPv4aaS deployments Single /24 but you NEED that ASN first ! From: Owen DeLong > Sent: 14 October 2025 11:44 To: Noah > Cc: Ben Roberts AfriNIC >; Andrew Alston >; RPD > Subject: Re: [rpd] Questions about IP Allocation rate Or better yet, not reserving IPv4 could spur those governments to deploy their govnets on IPv6 from the beginning with a clean greenfield design leapfrogging past the legacy baggage inherent in any IPv4 based solution. Owen On Oct 13, 2025, at 12:26, Noah > wrote: ? Ben There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. Cheers, ./noah On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. Sent from my iPhone On 13 Oct 2025, at 20:01, Noah > wrote: ? 54 African States are taking public services online. Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. Each of the 54 African states need address space indepedent of LIR space in each sovereign state. These are not ideas that actors in the private sector care about or think about. Cheers, ./noah On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 10:55:51 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 13:55:51 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: Any government who is doing DPI needs to wake up and get a reality check. Right now we are seeing a huge uptick in adoption of QUIC and TLS3 + ESNI - and once you deploy TLS3 with encrypted SNI deep packet inspection is as good as dead. In a presentation at RIPE by Cisco - they also acknowledged that DPI was a dying game and with the levels of encryption and the use of encrypted SNI, essentially such systems are made entirely useless. Andrew On Tue, Oct 14, 2025 at 1:34?PM Noah wrote: > Andrew > > At the back of your response to Ben... I know of a government operator > that hosts an on-net CF instance but luckly, they have their own INR and > dont necessary use CF IPs since CF supports BYOIP.. > > BYOIP means a govnet needs to have its own cocktail of v4/v6/ASN > > And the statistics should be able to show us how many of our own Govt who > are working on DPI can actually BYOIP? > > Cheers, > *.**/noah* > > > On Tue, 14 Oct 2025, 1:02?pm Andrew Alston, wrote: > >> Not Necessarily Ben. >> >> Reality is they could back end Government Networks with V6 and front the >> services with V4 which map to the V6 backend. >> >> This would substantially reduce the amount of IPv4 space actually needed >> by the governments, and provide dual-stack from the start. I have serious >> doubts that you will find governments in Africa requiring external access >> to more than 200+ unique services (which would represent a single /24 on >> the front end). >> >> We also need to keep in mind that many government services are now hosted >> behind the likes of CloudFlare - specifically for DDoS prevention >> mechanisms - and I'm not sure that IPv4 allocations by government entities >> are necessarily a good indicator of digital migration, since these services >> are not hosted on IPv4 space allocated to those entities. The same applies >> to services hosted in any of the major cloud providers. >> >> Considering the front ending of these services by the DDoS filter >> providers and the like - the requirement for front end IPv4 per government >> in terms of services to the citizenship is actually relatively small (And >> certainly does not warrant reservations at the level they are at - which - >> as I pointed out in an earlier message seem to be far higher than what is >> actually called for in the CPM) >> >> Thanks >> >> Andrew >> >> >> On Tue, Oct 14, 2025 at 12:55?PM wrote: >> >>> Owen, >>> >>> Will that not exclude many of their their citizens from accessing >>> digital services? >>> >>> >>> >>> >>> >>> >>> >>> *From:* Owen DeLong >>> *Sent:* 14 October 2025 11:44 >>> *To:* Noah >>> *Cc:* Ben Roberts AfriNIC ; Andrew Alston < >>> aa at alstonnetworks.net>; RPD >>> *Subject:* Re: [rpd] Questions about IP Allocation rate >>> >>> >>> >>> Or better yet, not reserving IPv4 could spur those governments to deploy >>> their govnets on IPv6 from the beginning with a clean greenfield design >>> leapfrogging past the legacy baggage inherent in any IPv4 based solution. >>> >>> >>> >>> Owen >>> >>> >>> >>> >>> >>> On Oct 13, 2025, at 12:26, Noah wrote: >>> >>> ? >>> >>> Ben >>> >>> >>> >>> There is critical structural challenge in the continents digital >>> landscape and you more than anyone knows this very well that we also suffer >>> from uneven maturity of Digital Public Infrastructure and Government >>> Networks (GovNet), which directly impacts the equitable deployment of >>> essential digital services across majority of countries across our >>> continent. >>> >>> >>> >>> Look we are talking about numbering infrastructure that would support >>> services like e-government, digital IDs, and public/private data exchanges, >>> while aligning with AFRINIC's exhaustion-phase policies. >>> >>> >>> >>> We can not shy away from these reality or pretend that there is lack of >>> foresight from actors at Afrinic and the community at large. >>> >>> >>> >>> Its a known fact that many of our African governments lack operational >>> GovNets and strategic reservations of IPv4 address space from AFRINIC could >>> serve as a targeted incentive to bridge these gaps. >>> >>> >>> >>> >>> >>> >>> >>> Cheers, >>> >>> *./noah* >>> >>> >>> >>> >>> >>> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < >>> ben.roberts at afrinic.net> wrote: >>> >>> I think The DPI systems are normally run by state owned digital agency >>> entities which are already mostly LIRs having some space. It is not quite >>> as you describe being state owned LIRs that have sovereign owned IPs that >>> are independent of LIRs.. >>> >>> >>> >>> >>> >>> >>> >>> Sent from my iPhone >>> >>> >>> >>> On 13 Oct 2025, at 20:01, Noah wrote: >>> >>> ? >>> >>> 54 African States are taking public services online. >>> >>> >>> >>> Digital Public infrastructure (DPI) is nolonger an idea. Its a real >>> thing. DPI is critical. The private sector will tap into that >>> infrastructure. Its here now. >>> >>> >>> >>> Each of the 54 African states need address space indepedent of LIR space >>> in each sovereign state. >>> >>> >>> >>> These are not ideas that actors in the private sector care about or >>> think about. >>> >>> >>> >>> Cheers, >>> >>> *./noah* >>> >>> >>> >>> >>> >>> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, >>> wrote: >>> >>> Hi All, >>> >>> >>> >>> I was wondering if there were updated statistics for the amount of space >>> allocated in the last 3 years. In addition to this information regarding >>> exactly how much free space is still available in the IPv4 unallocated pool >>> (excluding reservations) >>> >>> >>> >>> I ask this because depending on the allocation rate - we may wish to >>> consider revising the soft-landing policy that currently reserves a /12 >>> worth of ipv4 space for "future uses, as yet unforeseen". >>> >>> >>> >>> I point out that the soft landing policy was ratified in 2011, and if we >>> still, after 14 years, have not been able to articulate a clear reason for >>> such a large reservation, I think it's time we look at most, if not all, of >>> that /12 back into the main unallocated pool that can be allocated for >>> African resource holders that actually need it. >>> >>> >>> >>> Amongst other reasons, sitting with unallocated, unannounced, reserved >>> space like this leaves the space vulnerable to hijacking and malicious use >>> or even potential theft. >>> >>> >>> >>> Thanks >>> >>> >>> >>> Andrew >>> >>> >>> >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Tue Oct 14 11:02:09 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Tue, 14 Oct 2025 14:02:09 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: <18f201dc3cf9$fd489d30$f7d9d790$@afrinic.net> Andrew, DPI = Digital Public Infrastructure ? in the context Noah is talking. Not what you are thinking! From: Andrew Alston Sent: 14 October 2025 13:56 To: Noah Cc: Andrew Alston ; Ben Roberts - AfriNIC ; Owen DeLong ; RPD Subject: Re: [rpd] Questions about IP Allocation rate Any government who is doing DPI needs to wake up and get a reality check. Right now we are seeing a huge uptick in adoption of QUIC and TLS3 + ESNI - and once you deploy TLS3 with encrypted SNI deep packet inspection is as good as dead. In a presentation at RIPE by Cisco - they also acknowledged that DPI was a dying game and with the levels of encryption and the use of encrypted SNI, essentially such systems are made entirely useless. Andrew On Tue, Oct 14, 2025 at 1:34?PM Noah > wrote: Andrew At the back of your response to Ben... I know of a government operator that hosts an on-net CF instance but luckly, they have their own INR and dont necessary use CF IPs since CF supports BYOIP.. BYOIP means a govnet needs to have its own cocktail of v4/v6/ASN And the statistics should be able to show us how many of our own Govt who are working on DPI can actually BYOIP? Cheers, ./noah On Tue, 14 Oct 2025, 1:02?pm Andrew Alston, > wrote: Not Necessarily Ben. Reality is they could back end Government Networks with V6 and front the services with V4 which map to the V6 backend. This would substantially reduce the amount of IPv4 space actually needed by the governments, and provide dual-stack from the start. I have serious doubts that you will find governments in Africa requiring external access to more than 200+ unique services (which would represent a single /24 on the front end). We also need to keep in mind that many government services are now hosted behind the likes of CloudFlare - specifically for DDoS prevention mechanisms - and I'm not sure that IPv4 allocations by government entities are necessarily a good indicator of digital migration, since these services are not hosted on IPv4 space allocated to those entities. The same applies to services hosted in any of the major cloud providers. Considering the front ending of these services by the DDoS filter providers and the like - the requirement for front end IPv4 per government in terms of services to the citizenship is actually relatively small (And certainly does not warrant reservations at the level they are at - which - as I pointed out in an earlier message seem to be far higher than what is actually called for in the CPM) Thanks Andrew On Tue, Oct 14, 2025 at 12:55?PM > wrote: Owen, Will that not exclude many of their their citizens from accessing digital services? From: Owen DeLong > Sent: 14 October 2025 11:44 To: Noah > Cc: Ben Roberts AfriNIC >; Andrew Alston >; RPD > Subject: Re: [rpd] Questions about IP Allocation rate Or better yet, not reserving IPv4 could spur those governments to deploy their govnets on IPv6 from the beginning with a clean greenfield design leapfrogging past the legacy baggage inherent in any IPv4 based solution. Owen On Oct 13, 2025, at 12:26, Noah > wrote: ? Ben There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. Cheers, ./noah On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. Sent from my iPhone On 13 Oct 2025, at 20:01, Noah > wrote: ? 54 African States are taking public services online. Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. Each of the 54 African states need address space indepedent of LIR space in each sovereign state. These are not ideas that actors in the private sector care about or think about. Cheers, ./noah On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 11:03:17 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 14:03:17 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <18f201dc3cf9$fd489d30$f7d9d790$@afrinic.net> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> <18f201dc3cf9$fd489d30$f7d9d790$@afrinic.net> Message-ID: Aahhh my apologies :) Sorry - I just happen to know that certain governments are attempting DPI (Deep Packet Inspection) on links hence my misreading the acronym. Andrew On Tue, Oct 14, 2025 at 2:02?PM wrote: > Andrew, > > > > DPI = Digital Public Infrastructure ? in the context Noah is talking. > > > > Not what you are thinking! > > > > *From:* Andrew Alston > *Sent:* 14 October 2025 13:56 > *To:* Noah > *Cc:* Andrew Alston ; Ben Roberts - AfriNIC < > ben.roberts at afrinic.net>; Owen DeLong ; RPD < > rpd at afrinic.net> > *Subject:* Re: [rpd] Questions about IP Allocation rate > > > > Any government who is doing DPI needs to wake up and get a reality check. > > > > Right now we are seeing a huge uptick in adoption of QUIC and TLS3 + ESNI > - and once you deploy TLS3 with encrypted SNI deep packet inspection is as > good as dead. > > > > In a presentation at RIPE by Cisco - they also acknowledged that DPI was a > dying game and with the levels of encryption and the use of encrypted SNI, > essentially such systems are made entirely useless. > > > > Andrew > > > > > > On Tue, Oct 14, 2025 at 1:34?PM Noah wrote: > > Andrew > > > > At the back of your response to Ben... I know of a government operator > that hosts an on-net CF instance but luckly, they have their own INR and > dont necessary use CF IPs since CF supports BYOIP.. > > > > BYOIP means a govnet needs to have its own cocktail of v4/v6/ASN > > > > And the statistics should be able to show us how many of our own Govt who > are working on DPI can actually BYOIP? > > > > Cheers, > > *./noah* > > > > > > On Tue, 14 Oct 2025, 1:02?pm Andrew Alston, wrote: > > Not Necessarily Ben. > > > > Reality is they could back end Government Networks with V6 and front the > services with V4 which map to the V6 backend. > > > > This would substantially reduce the amount of IPv4 space actually needed > by the governments, and provide dual-stack from the start. I have serious > doubts that you will find governments in Africa requiring external access > to more than 200+ unique services (which would represent a single /24 on > the front end). > > > > We also need to keep in mind that many government services are now hosted > behind the likes of CloudFlare - specifically for DDoS prevention > mechanisms - and I'm not sure that IPv4 allocations by government entities > are necessarily a good indicator of digital migration, since these services > are not hosted on IPv4 space allocated to those entities. The same applies > to services hosted in any of the major cloud providers. > > > > Considering the front ending of these services by the DDoS filter > providers and the like - the requirement for front end IPv4 per government > in terms of services to the citizenship is actually relatively small (And > certainly does not warrant reservations at the level they are at - which - > as I pointed out in an earlier message seem to be far higher than what is > actually called for in the CPM) > > > > Thanks > > > > Andrew > > > > > > On Tue, Oct 14, 2025 at 12:55?PM wrote: > > Owen, > > Will that not exclude many of their their citizens from accessing digital > services? > > > > > > > > *From:* Owen DeLong > *Sent:* 14 October 2025 11:44 > *To:* Noah > *Cc:* Ben Roberts AfriNIC ; Andrew Alston < > aa at alstonnetworks.net>; RPD > *Subject:* Re: [rpd] Questions about IP Allocation rate > > > > Or better yet, not reserving IPv4 could spur those governments to deploy > their govnets on IPv6 from the beginning with a clean greenfield design > leapfrogging past the legacy baggage inherent in any IPv4 based solution. > > > > Owen > > > > > > On Oct 13, 2025, at 12:26, Noah wrote: > > ? > > Ben > > > > There is critical structural challenge in the continents digital landscape > and you more than anyone knows this very well that we also suffer from > uneven maturity of Digital Public Infrastructure and Government Networks > (GovNet), which directly impacts the equitable deployment of essential > digital services across majority of countries across our continent. > > > > Look we are talking about numbering infrastructure that would support > services like e-government, digital IDs, and public/private data exchanges, > while aligning with AFRINIC's exhaustion-phase policies. > > > > We can not shy away from these reality or pretend that there is lack of > foresight from actors at Afrinic and the community at large. > > > > Its a known fact that many of our African governments lack operational > GovNets and strategic reservations of IPv4 address space from AFRINIC could > serve as a targeted incentive to bridge these gaps. > > > > > > > > Cheers, > > *./noah* > > > > > > On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < > ben.roberts at afrinic.net> wrote: > > I think The DPI systems are normally run by state owned digital agency > entities which are already mostly LIRs having some space. It is not quite > as you describe being state owned LIRs that have sovereign owned IPs that > are independent of LIRs.. > > > > > > > > Sent from my iPhone > > > > On 13 Oct 2025, at 20:01, Noah wrote: > > ? > > 54 African States are taking public services online. > > > > Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. > DPI is critical. The private sector will tap into that infrastructure. Its > here now. > > > > Each of the 54 African states need address space indepedent of LIR space > in each sovereign state. > > > > These are not ideas that actors in the private sector care about or think > about. > > > > Cheers, > > *./noah* > > > > > > On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, wrote: > > Hi All, > > > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > > > Thanks > > > > Andrew > > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 11:31:52 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 14:31:52 +0300 Subject: [rpd] The IPv4 Country Allocation Poverty line in Africa. In-Reply-To: <16fa01dc3cef$b2330290$169907b0$@afrinic.net> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <16fa01dc3cef$b2330290$169907b0$@afrinic.net> Message-ID: Hi Ben Thanks for the research and writeup.. the below conclusion reasonates and more than any time... as you have rightly pointed out... " For AfriNIC and Regional Organizations: - Support Internet infrastructure development in underserved regions " The above need to form part of the most important strategic goals the registry shall have to undertake inline with section 3 of the current Afrinic Bylaws. One way to support underserved regions would be to reform AFGWG and also make it a deliberate objective to go out of the way to work with leaders in those countries. Afrinic must spend less time and energy in countries that are in green color. Noah Cheers, *.**/noah* On Tue, 14 Oct 2025, 2:02?pm ben.roberts--- via RPD, wrote: > All, > > > > Please find attached the analysed data of IPv4 allocation per capita, > along with an interactive HTML map? Along with a link to my latest blog.. > > > > IPv4 Address Allocation in Africa: Are you above or Below the IP Address > Poverty Line ? > > This analysis examines IPv4 address allocation per capita across 56 > African countries using data from AfriNIC (African Network Information > Centre) resource allocation statistics for 2025. The findings reveal a > stark digital divide, with allocation rates varying by a factor of nearly > 60,000 between the best and worst-served nations. > > > > > https://www.digitaleconomy.ke/post/ipv4-address-allocation-in-africa-are-you-above-or-below-the-ip-address-poverty-line > > > > Cheers > > Ben > > > > > > *From:* Noah > *Sent:* 14 October 2025 12:20 > *To:* Owen DeLong > *Cc:* Ben Roberts AfriNIC ; Andrew Alston < > aa at alstonnetworks.net>; RPD > *Subject:* Re: [rpd] Questions about IP Allocation rate > > > > Its easier to say it would be nice to see folks deploy IPv6 until you > realise ...Ooh wait a minute..Ops IPv4 transfer markets still exists. > > > > That most of internet traffic is still IPv4 powered and almost all > software is writted with IPv4 in mind and lots of applications dont > support IPv6. > > > > And then you also realise that In Africa unlike the Global North, the cost > effective access technology does not support DHCPv6 or DS-Lite and that > until recently even Windows OS let alone Android has issues with supporting > CLAT on most personal handsets. > > > > Linux is not mainstream desktop OS in Africa. Most of the secondhand used > PC comes preinstalled with outdated Windows OS. > > > > Cheers, > > *./noah* > > > > > > On Tue, 14 Oct 2025, 11:44?am Owen DeLong, wrote: > > Or better yet, not reserving IPv4 could spur those governments to deploy > their govnets on IPv6 from the beginning with a clean greenfield design > leapfrogging past the legacy baggage inherent in any IPv4 based solution. > > > > Owen > > > > > > On Oct 13, 2025, at 12:26, Noah wrote: > > ? > > Ben > > > > There is critical structural challenge in the continents digital landscape > and you more than anyone knows this very well that we also suffer from > uneven maturity of Digital Public Infrastructure and Government Networks > (GovNet), which directly impacts the equitable deployment of essential > digital services across majority of countries across our continent. > > > > Look we are talking about numbering infrastructure that would support > services like e-government, digital IDs, and public/private data exchanges, > while aligning with AFRINIC's exhaustion-phase policies. > > > > We can not shy away from these reality or pretend that there is lack of > foresight from actors at Afrinic and the community at large. > > > > Its a known fact that many of our African governments lack operational > GovNets and strategic reservations of IPv4 address space from AFRINIC could > serve as a targeted incentive to bridge these gaps. > > > > > > > > Cheers, > > *./noah* > > > > > > On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < > ben.roberts at afrinic.net> wrote: > > I think The DPI systems are normally run by state owned digital agency > entities which are already mostly LIRs having some space. It is not quite > as you describe being state owned LIRs that have sovereign owned IPs that > are independent of LIRs.. > > > > > > > > Sent from my iPhone > > > > On 13 Oct 2025, at 20:01, Noah wrote: > > ? > > 54 African States are taking public services online. > > > > Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. > DPI is critical. The private sector will tap into that infrastructure. Its > here now. > > > > Each of the 54 African states need address space indepedent of LIR space > in each sovereign state. > > > > These are not ideas that actors in the private sector care about or think > about. > > > > Cheers, > > *./noah* > > > > > > On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, wrote: > > Hi All, > > > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > > > Thanks > > > > Andrew > > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 11:38:53 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 14:38:53 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> Message-ID: On Tue, 14 Oct 2025, 1:46?pm jordi.palet--- via RPD, wrote: > > In both cases you need ?some? IPv4 addresses, and because you can?t route > less than /24, most of the time, you will use a /24. > This is a very important point. At bare minimum, that is the block folks want to see in the DFZ. As such, ISP sub-allocations with a longer prefix than /24 dont count if we are thinking strategically even though a single unicast v4 address can sythasize a good number of TCP ports... If you have multiple PoPs for your BGP upstreams, then you may need > multiple /24s. > That is why we settled for /22 in the softlanding policy. Noah > Regards, > Jordi > > @jordipalet > > > El 14 oct 2025, a las 12:19, Hendrik Visage > escribi?: > > > > On 14 Oct 2025, at 11:55, ben.roberts--- via RPD wrote: > > Owen, > Will that not exclude many of their their citizens from accessing digital > services? > > > 1) Get an ASN > 2) deply IPv6 network > 3) CGNAT / SIIT-DC / MAP-T - refer to Sky Networks?s presentations on > IPv4aaS deployments > > Single /24 but you NEED that ASN first ! > > > > > > *From:* Owen DeLong > *Sent:* 14 October 2025 11:44 > *To:* Noah > *Cc:* Ben Roberts AfriNIC ; Andrew Alston < > aa at alstonnetworks.net>; RPD > *Subject:* Re: [rpd] Questions about IP Allocation rate > > Or better yet, not reserving IPv4 could spur those governments to deploy > their govnets on IPv6 from the beginning with a clean greenfield design > leapfrogging past the legacy baggage inherent in any IPv4 based solution. > > Owen > > > > On Oct 13, 2025, at 12:26, Noah wrote: > > ? > Ben > > There is critical structural challenge in the continents digital landscape > and you more than anyone knows this very well that we also suffer from > uneven maturity of Digital Public Infrastructure and Government Networks > (GovNet), which directly impacts the equitable deployment of essential > digital services across majority of countries across our continent. > > Look we are talking about numbering infrastructure that would support > services like e-government, digital IDs, and public/private data exchanges, > while aligning with AFRINIC's exhaustion-phase policies. > > We can not shy away from these reality or pretend that there is lack of > foresight from actors at Afrinic and the community at large. > > Its a known fact that many of our African governments lack operational > GovNets and strategic reservations of IPv4 address space from AFRINIC could > serve as a targeted incentive to bridge these gaps. > > > > Cheers, > *./noah* > > > On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, < > ben.roberts at afrinic.net> wrote: > > I think The DPI systems are normally run by state owned digital agency > entities which are already mostly LIRs having some space. It is not quite > as you describe being state owned LIRs that have sovereign owned IPs that > are independent of LIRs.. > > > > Sent from my iPhone > > > On 13 Oct 2025, at 20:01, Noah wrote: > > ? > 54 African States are taking public services online. > > Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. > DPI is critical. The private sector will tap into that infrastructure. Its > here now. > > Each of the 54 African states need address space indepedent of LIR space > in each sovereign state. > > These are not ideas that actors in the private sector care about or think > about. > > Cheers, > *./noah* > > > On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, wrote: > > Hi All, > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > Thanks > > Andrew > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 11:41:50 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 14:41:50 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: On Tue, 14 Oct 2025, 1:56?pm Andrew Alston, wrote: > Any government who is doing DPI needs to wake up and get a reality check. > DPI as in Digital Public Infrastructure (egovt, digital-id, govnet, etc) > deep packet inspection is as good as dead. > Not that DPI bro... Noah > -------------- next part -------------- An HTML attachment was scrubbed... URL: From madhvi at afrinic.net Tue Oct 14 13:26:46 2025 From: madhvi at afrinic.net (Madhvi Gokool) Date: Tue, 14 Oct 2025 17:26:46 +0400 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> Message-ID: Dear Andrew The status 'Reserved' is provided to the following cases :- a) Resources that are reserved according to ratified and implemented policies(one /12 IPv4 under the soft landing policy and 2 x 16?s IPv4 prefixes? and small ASNs for IXPs) b) Resources that have been reclaimed from organisations during the closure exercises and quarantined c)?Resources that have been voluntarily returned? by resource members? and quarantined Quarantined resources in the case of b) and c) above are subject to a cleanup process to ensure sanity before they are added to the available pool of resources. d) Resources that have beenderegistered from the AFRINIC whois database after the investigation of misappropriated resources were also quarantined. We will produce a breakdown of these reservations by tomorrow. Regards Madhvi On 14/10/2025 13:11, Andrew Alston wrote: > Hi Madhvi, > > I'm a little confused by the stats on that page.? According to the CPM > AfriNIC currently reserves as a /16 for IXP space and a /12 under soft > landing.? This accounts for a total of 1,114,112 addresses. > > The stats page shows total reservations of 17509 /24s - which amounts > to roughly a /10 and another /14 in reserved space.? This is more than > 4 times the amount of reserved space that I can account for in the CPM > - so what is the rest of it and what am I missing here? > > Thanks > > Andrew > > > On Tue, Oct 14, 2025 at 11:03?AM Madhvi Gokool via RPD > wrote: > > Dear Sir > > AFRINIC publishes statistics here - https://stats.afrinic.net > > The graph titled ?Distribution of IPv4 (/24) per year? on the page > Statistics Portal can be > referenced for yearly distribution, In addition, The ?Filter by > date Range? can be used to get granular statistics for the IPv4 > allocations. > > We also wish to inform you that while the page is accessible on > Firefox and Safari browsers, we have noticed an erratic behaviour > when accessed via Chrome browser. We are investigating this > erratic behaviour at the moment. > > Kind Regards > > Madhvi Gokool > > AFRINIC Policy Liaison > > > On 13/10/2025 18:43, Andrew Alston wrote: >> Hi All, >> >> I was wondering if there were updated statistics for the amount >> of space allocated in the last 3 years.? In addition to this >> information regarding exactly how much free space is still >> available in the IPv4 unallocated pool (excluding reservations) >> >> I ask this because depending on the allocation rate - we may wish >> to consider revising the soft-landing policy that currently >> reserves a /12 worth of ipv4 space for "future uses, as yet >> unforeseen". >> >> I point out that the soft landing policy was ratified in 2011, >> and if we still, after 14 years, have not been able to articulate >> a clear reason for such a large reservation, I think it's time we >> look at most, if not all, of that /12 back into the main >> unallocated pool that can be allocated for African resource >> holders that actually need it. >> >> Amongst other reasons, sitting with unallocated, unannounced, >> reserved space like this leaves the space vulnerable to hijacking >> and malicious use or even potential theft. >> >> Thanks >> >> Andrew >> >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 13:45:44 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 16:45:44 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> Message-ID: Can you also please supply the ranges so that a BGP table audit can be done to ensure that these resources are indeed not being used inappropriately or illegally please. Andrew On Tue, 14 Oct 2025 at 16:27, Madhvi Gokool via RPD wrote: > Dear Andrew > > The status 'Reserved' is provided to the following cases :- > > a) Resources that are reserved according to ratified and implemented > policies(one /12 IPv4 under the soft landing policy and 2 x 16?s IPv4 > prefixes and small ASNs for IXPs) > > b) Resources that have been reclaimed from organisations during the > closure exercises and quarantined > > c) Resources that have been voluntarily returned by resource members and > quarantined > > Quarantined resources in the case of b) and c) above are subject to a > cleanup process to ensure sanity before they are added to the available > pool of resources. > > d) Resources that have been deregistered from the AFRINIC whois database > after the investigation of misappropriated resources were also quarantined. > > We will produce a breakdown of these reservations by tomorrow. > > Regards > > Madhvi > > > On 14/10/2025 13:11, Andrew Alston wrote: > > Hi Madhvi, > > I'm a little confused by the stats on that page. According to the CPM > AfriNIC currently reserves as a /16 for IXP space and a /12 under soft > landing. This accounts for a total of 1,114,112 addresses. > > The stats page shows total reservations of 17509 /24s - which amounts to > roughly a /10 and another /14 in reserved space. This is more than 4 times > the amount of reserved space that I can account for in the CPM - so what is > the rest of it and what am I missing here? > > Thanks > > Andrew > > > On Tue, Oct 14, 2025 at 11:03?AM Madhvi Gokool via RPD > wrote: > >> Dear Sir >> >> AFRINIC publishes statistics here - https://stats.afrinic.net >> >> The graph titled ?Distribution of IPv4 (/24) per year? on the page Statistics >> Portal can be referenced for yearly >> distribution, In addition, The ?Filter by date Range? can be used to get >> granular statistics for the IPv4 allocations. >> >> We also wish to inform you that while the page is accessible on Firefox >> and Safari browsers, we have noticed an erratic behaviour when accessed via >> Chrome browser. We are investigating this erratic behaviour at the moment. >> >> Kind Regards >> >> Madhvi Gokool >> >> AFRINIC Policy Liaison >> >> >> On 13/10/2025 18:43, Andrew Alston wrote: >> >> Hi All, >> >> I was wondering if there were updated statistics for the amount of space >> allocated in the last 3 years. In addition to this information regarding >> exactly how much free space is still available in the IPv4 unallocated pool >> (excluding reservations) >> >> I ask this because depending on the allocation rate - we may wish to >> consider revising the soft-landing policy that currently reserves a /12 >> worth of ipv4 space for "future uses, as yet unforeseen". >> >> I point out that the soft landing policy was ratified in 2011, and if we >> still, after 14 years, have not been able to articulate a clear reason for >> such a large reservation, I think it's time we look at most, if not all, of >> that /12 back into the main unallocated pool that can be allocated for >> African resource holders that actually need it. >> >> Amongst other reasons, sitting with unallocated, unannounced, reserved >> space like this leaves the space vulnerable to hijacking and malicious use >> or even potential theft. >> >> Thanks >> >> Andrew >> >> >> >> _______________________________________________ >> RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregoire.ehoumi at yahoo.fr Tue Oct 14 13:46:24 2025 From: gregoire.ehoumi at yahoo.fr (=?utf-8?Q?Gr=C3=A9goire_EHOUMI?=) Date: Tue, 14 Oct 2025 09:46:24 -0400 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <5DF5ED45-A4B2-4DEB-B279-A7C045495500@wacren.net> References: <5DF5ED45-A4B2-4DEB-B279-A7C045495500@wacren.net> Message-ID: <44830741-6C2C-44D5-BBBA-369ACCF19838@yahoo.fr> Hello, > On Oct 12, 2025, at 6:31?AM, Omo Oaiya via RPD wrote: > > ? > It?s great to see discussion back on the list, a good sign that the community spirit is still strong. I agree with Owen. What really matters is that the feedback loop stays open, clear, and timely. > > On Ben?s point, participation will grow if we make the PDP more inclusive and relevant. We should bring in people from IXPs, NRENs, academia, civil society, and sectors shaping Africa?s digital economy. Linking policy work to that wider digital transformation agenda will draw new energy and perspectives. > > Let?s keep it going. > > Best, > Omo > ?More inclusive? by offering a pleasant, productive PDP to the expected standards, right ? Policy discussions and meetings have always been open to anyone to join and participate. No one has been prevented from participating in pdp, except perhaps our behaviours may have discouraged, scared away many people in our diverse and fragile ecosystem. The board made a key prerequisite to resumption of PDP as below: "A key prerequisite will be to ensure that all community mailing lists maintain an atmosphere of civility and constructive engagement." Governments are more attentive now, watching and assessing us. It shouldn't be like before thanks for our collective efforts. ?More relevant? yes towards policy making for Number resources management, but without turning the PDP into an IG forum? Community, members, board and staff should make sure that policies we discuss and approve serve the interests AFRICA and not private, personal interests. Cheers, - Gr?goire -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Tue Oct 14 13:55:48 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Tue, 14 Oct 2025 16:55:48 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> Message-ID: Alternatively to the below - can you supply a list of every range currently assigned to AfriNIC - inclusive of legacy blocks - and I will script an audit of those blocks vs the data on the IPv4 stats download. This will avoid explicitly exposing reserved blocks but will still allow such a BGP audit to be done Andrew On Tue, 14 Oct 2025 at 16:45, Andrew Alston wrote: > Can you also please supply the ranges so that a BGP table audit can be > done to ensure that these resources are indeed not being used > inappropriately or illegally please. > > Andrew > > On Tue, 14 Oct 2025 at 16:27, Madhvi Gokool via RPD > wrote: > >> Dear Andrew >> >> The status 'Reserved' is provided to the following cases :- >> >> a) Resources that are reserved according to ratified and implemented >> policies(one /12 IPv4 under the soft landing policy and 2 x 16?s IPv4 >> prefixes and small ASNs for IXPs) >> >> b) Resources that have been reclaimed from organisations during the >> closure exercises and quarantined >> >> c) Resources that have been voluntarily returned by resource members >> and quarantined >> >> Quarantined resources in the case of b) and c) above are subject to a >> cleanup process to ensure sanity before they are added to the available >> pool of resources. >> >> d) Resources that have been deregistered from the AFRINIC whois database >> after the investigation of misappropriated resources were also quarantined. >> >> We will produce a breakdown of these reservations by tomorrow. >> >> Regards >> >> Madhvi >> >> >> On 14/10/2025 13:11, Andrew Alston wrote: >> >> Hi Madhvi, >> >> I'm a little confused by the stats on that page. According to the CPM >> AfriNIC currently reserves as a /16 for IXP space and a /12 under soft >> landing. This accounts for a total of 1,114,112 addresses. >> >> The stats page shows total reservations of 17509 /24s - which amounts to >> roughly a /10 and another /14 in reserved space. This is more than 4 times >> the amount of reserved space that I can account for in the CPM - so what is >> the rest of it and what am I missing here? >> >> Thanks >> >> Andrew >> >> >> On Tue, Oct 14, 2025 at 11:03?AM Madhvi Gokool via RPD >> wrote: >> >>> Dear Sir >>> >>> AFRINIC publishes statistics here - https://stats.afrinic.net >>> >>> The graph titled ?Distribution of IPv4 (/24) per year? on the page Statistics >>> Portal can be referenced for yearly >>> distribution, In addition, The ?Filter by date Range? can be used to get >>> granular statistics for the IPv4 allocations. >>> >>> We also wish to inform you that while the page is accessible on Firefox >>> and Safari browsers, we have noticed an erratic behaviour when accessed via >>> Chrome browser. We are investigating this erratic behaviour at the moment. >>> >>> Kind Regards >>> >>> Madhvi Gokool >>> >>> AFRINIC Policy Liaison >>> >>> >>> On 13/10/2025 18:43, Andrew Alston wrote: >>> >>> Hi All, >>> >>> I was wondering if there were updated statistics for the amount of space >>> allocated in the last 3 years. In addition to this information regarding >>> exactly how much free space is still available in the IPv4 unallocated pool >>> (excluding reservations) >>> >>> I ask this because depending on the allocation rate - we may wish to >>> consider revising the soft-landing policy that currently reserves a /12 >>> worth of ipv4 space for "future uses, as yet unforeseen". >>> >>> I point out that the soft landing policy was ratified in 2011, and if we >>> still, after 14 years, have not been able to articulate a clear reason for >>> such a large reservation, I think it's time we look at most, if not all, of >>> that /12 back into the main unallocated pool that can be allocated for >>> African resource holders that actually need it. >>> >>> Amongst other reasons, sitting with unallocated, unannounced, reserved >>> space like this leaves the space vulnerable to hijacking and malicious use >>> or even potential theft. >>> >>> Thanks >>> >>> Andrew >>> >>> >>> >>> _______________________________________________ >>> RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 15:14:52 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 08:14:52 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> Message-ID: <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen > On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: > > ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. > > Regards, > Jordi > > @jordipalet > > >> El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: >> >> Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. >> >> Owen >> >> >>>> On Oct 14, 2025, at 01:22, Hendrik Visage wrote: >>>> >>> ? Question: >>> >>> Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? >>> >>> ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. >>> >>> Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" >>> >>> --- >>> Hendrik Visage >>> Instant messaging: https://t.me/hvisage >>> >>> >>>> On 13 Oct 2025, at 16:43, Andrew Alston wrote: >>>> >>>> Hi All, >>>> >>>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>>> >>>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>>> >>>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>>> >>>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>>> >>>> Thanks >>>> >>>> Andrew >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> --- >>> >>> Hendrik Visage >>> >>> hvisage at hevis.co.za >>> >>> >>> HeViS.Co Systems Pty Ltd >>> >>> https://www.envisage.co.za >>> >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 15:18:36 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 08:18:36 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: <32394350-E60D-4674-A973-016A7712E053@delong.com> An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Tue Oct 14 16:06:14 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Tue, 14 Oct 2025 18:06:14 +0200 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> Message-ID: <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet > El 14 oct 2025, a las 17:14, Owen DeLong escribi?: > > If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. > > Owen > > >> On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: >> >> ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. >> >> Regards, >> Jordi >> >> @jordipalet >> >> >>> El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: >>> >>> Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. >>> >>> Owen >>> >>> >>>> On Oct 14, 2025, at 01:22, Hendrik Visage wrote: >>>> >>>> ? Question: >>>> >>>> Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? >>>> >>>> ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. >>>> >>>> Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" >>>> >>>> --- >>>> Hendrik Visage >>>> Instant messaging: https://t.me/hvisage >>>> >>>> >>>>> On 13 Oct 2025, at 16:43, Andrew Alston wrote: >>>>> >>>>> Hi All, >>>>> >>>>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>>>> >>>>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>>>> >>>>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>>>> >>>>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>>>> >>>>> Thanks >>>>> >>>>> Andrew >>>>> >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> --- >>>> >>>> Hendrik Visage >>>> >>>> hvisage at hevis.co.za >>>> >>>> >>>> HeViS.Co Systems Pty Ltd >>>> >>>> https://www.envisage.co.za >>>> >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Tue Oct 14 16:58:24 2025 From: sami.salih at outlook.com (Sami Salih) Date: Tue, 14 Oct 2025 16:58:24 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> Message-ID: That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. Sami Salih, Sent from Outlook for Android ________________________________ From: jordi.palet--- via RPD Sent: Tuesday, October 14, 2025 7:06:14 PM To: RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet El 14 oct 2025, a las 17:14, Owen DeLong escribi?: If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen On Oct 14, 2025, at 01:22, Hendrik Visage wrote: ? Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Tue Oct 14 17:33:55 2025 From: noah at neo.co.tz (Noah) Date: Tue, 14 Oct 2025 20:33:55 +0300 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> Message-ID: On Tue, 14 Oct 2025, 8:10?pm Sami Salih, wrote: > That said, relying on African governments may be reasonable for countries > with stable economic and political conditions. However, given the conflicts > and instability present in several regions across the continent, it's wise > to preserve sufficient resources for future generations, who may otherwise > face significant scarcity. > A classic example in contemporary african history is states that suffered prolonged civil wars such as Somalia, South Sudan, Burundi, Sierra Leon to name but a few whose pacification is as recent as a decade ago with some sense of peace & political stability starting to emerge. On a related note, the reserved IP blocks come at no cost. They don?t > require active maintenance or storage infrastructure, just basic protection > against misuse or hijacking. These reserves can be kept indefinitely. And > once IPv6 becomes the dominant protocol, we can simply "let them go!". But > for now, we need to keep our resources. > 100% and this is the sorf of foresight that most actors both within Afrinic and the internet community does not seem to grasp. If we can reserve space for critical Infra such as IXP's then policy development should always be guided by a considerable number of socio-economic factors. Mwalimu Nyerere once stated to the nation that, look, those minerals that we cant exploit today, can always be exploited later in futute when posterity is ready and knowledgable enough to make good sense of them after all, they dont expire. Its now 5 decades later and with education, information and exposure, the people are now able to use the raw-material and build industry locally. Foresight my people, foresight. We are internet engineers yes but we must think beyond just engineering. Noah > Sami Salih, > > > Sent from Outlook for Android > ------------------------------ > *From:* jordi.palet--- via RPD > *Sent:* Tuesday, October 14, 2025 7:06:14 PM > *To:* RPD > *Subject:* Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate > > I would agree with you if all the economies have the same resources (not > just economical ones, but also human resources, expertise, etc.), but we > know is not the case. > > Now a different history is if any ISP in 1-2 years from now, has not *at > least* started their deployment plans. In such a situation, I think it is a > clear matter of governments, in their duty to protect citizens, taking > strong actions against any service provider or industry not doing so. Of > course that means the government networks itself need to use IPv6: they > need to set the example, otherwise you can?t enforce it. > > Today deploying a *new* network using 464XLAT is even cheaper and easier > than doing so with IPv4 or dual-stack. So this must be clearly enforced to > obtain new licenses, as there is no excuse. This is valid for either > cellular networks, broadband networks or even for enterprise networks using > IPv6-mostly. > > I fully understand that is not the same for an existing network, that?s > why they should have some more time, but at least have *clearly structured* > plans, not just ?yes we are thinking on that? ... > > Saludos, > Jordi > > @jordipalet > > > El 14 oct 2025, a las 17:14, Owen DeLong escribi?: > > If it isn?t already deployed, I question this at this point. How long > should the rest of the internet subsidize failure to deploy? Personally, I > think we are past that point. > > Owen > > > On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: > > ?Agree, however, we know very well that a small IPv4 pool (may be a /24 > for each BGP PoP), is needed for interconnection with IPv4 Internet, as > there may be still some old apps that require it. > > Regards, > Jordi > > @jordipalet > > > El 14 oct 2025, a las 10:46, Owen DeLong via RPD > escribi?: > > Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and > the efforts to keep it from running out are actually counterproductive to > progress in the African digital economy. > > Owen > > > On Oct 14, 2025, at 01:22, Hendrik Visage wrote: > > ? Question: > > Shouldn?t we rather consider pushing IPv6 deployment assistance across > Africa? ie. let the rest of the IPv4 go ASAP without much resistance > instead of making this a begging/pleading/fighting game? > > ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 > roll outs, ?cause they don?t have any left, and looking at AfriNIC services > countries, we are still have an abundance of IPv4, so IPv6 percentage roll > outs are very low, and rathe we should be pushing to mirror the IPv6 > percentage rollout and usage rather than fighting over the few remaining > IPv4s if we want to grow digital rollouts. > > Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven > a complete IPv6 rollout can you get anymore IPv4" > > --- > Hendrik Visage > Instant messaging: https://t.me/hvisage > > > On 13 Oct 2025, at 16:43, Andrew Alston wrote: > > Hi All, > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > Thanks > > Andrew > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From seun.ojedeji at gmail.com Tue Oct 14 18:08:02 2025 From: seun.ojedeji at gmail.com (Seun Ojedeji) Date: Tue, 14 Oct 2025 13:08:02 -0500 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> Message-ID: Good points Sami, but I am not a fan of leaving it indefinitely, that will make it become useless to generation to come nor will it be useful for present generation. So long as there are legitimate need/use for v4 at the moment, it make sense at some point in the near future to use the reserve. This can be through tieing allocation to a more intentional or aggressive V6 deployment requirements. A policy that makes v4 to be an add-on to V6 allocation/deployment may be a good use of the reserved space. Otherwise the future generation which will be more V6 aware/exposed than you and I may not find so many use cases for v4 at their time. Regards ---- Sent from my mobile kindly excuse typos On Tue, 14 Oct 2025, 11:59?am Sami Salih, wrote: > That said, relying on African governments may be reasonable for countries > with stable economic and political conditions. However, given the conflicts > and instability present in several regions across the continent, it's wise > to preserve sufficient resources for future generations, who may otherwise > face significant scarcity. > On a related note, the reserved IP blocks come at no cost. They don?t > require active maintenance or storage infrastructure, just basic protection > against misuse or hijacking. These reserves can be kept indefinitely. And > once IPv6 becomes the dominant protocol, we can simply "let them go!". But > for now, we need to keep our resources. > > Sami Salih, > > > Sent from Outlook for Android > ------------------------------ > *From:* jordi.palet--- via RPD > *Sent:* Tuesday, October 14, 2025 7:06:14 PM > *To:* RPD > *Subject:* Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate > > I would agree with you if all the economies have the same resources (not > just economical ones, but also human resources, expertise, etc.), but we > know is not the case. > > Now a different history is if any ISP in 1-2 years from now, has not *at > least* started their deployment plans. In such a situation, I think it is a > clear matter of governments, in their duty to protect citizens, taking > strong actions against any service provider or industry not doing so. Of > course that means the government networks itself need to use IPv6: they > need to set the example, otherwise you can?t enforce it. > > Today deploying a *new* network using 464XLAT is even cheaper and easier > than doing so with IPv4 or dual-stack. So this must be clearly enforced to > obtain new licenses, as there is no excuse. This is valid for either > cellular networks, broadband networks or even for enterprise networks using > IPv6-mostly. > > I fully understand that is not the same for an existing network, that?s > why they should have some more time, but at least have *clearly structured* > plans, not just ?yes we are thinking on that? ... > > Saludos, > Jordi > > @jordipalet > > > El 14 oct 2025, a las 17:14, Owen DeLong escribi?: > > If it isn?t already deployed, I question this at this point. How long > should the rest of the internet subsidize failure to deploy? Personally, I > think we are past that point. > > Owen > > > On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: > > ?Agree, however, we know very well that a small IPv4 pool (may be a /24 > for each BGP PoP), is needed for interconnection with IPv4 Internet, as > there may be still some old apps that require it. > > Regards, > Jordi > > @jordipalet > > > El 14 oct 2025, a las 10:46, Owen DeLong via RPD > escribi?: > > Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and > the efforts to keep it from running out are actually counterproductive to > progress in the African digital economy. > > Owen > > > On Oct 14, 2025, at 01:22, Hendrik Visage wrote: > > ? Question: > > Shouldn?t we rather consider pushing IPv6 deployment assistance across > Africa? ie. let the rest of the IPv4 go ASAP without much resistance > instead of making this a begging/pleading/fighting game? > > ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 > roll outs, ?cause they don?t have any left, and looking at AfriNIC services > countries, we are still have an abundance of IPv4, so IPv6 percentage roll > outs are very low, and rathe we should be pushing to mirror the IPv6 > percentage rollout and usage rather than fighting over the few remaining > IPv4s if we want to grow digital rollouts. > > Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven > a complete IPv6 rollout can you get anymore IPv4" > > --- > Hendrik Visage > Instant messaging: https://t.me/hvisage > > > On 13 Oct 2025, at 16:43, Andrew Alston wrote: > > Hi All, > > I was wondering if there were updated statistics for the amount of space > allocated in the last 3 years. In addition to this information regarding > exactly how much free space is still available in the IPv4 unallocated pool > (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a /12 > worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if we > still, after 14 years, have not been able to articulate a clear reason for > such a large reservation, I think it's time we look at most, if not all, of > that /12 back into the main unallocated pool that can be allocated for > African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious use > or even potential theft. > > Thanks > > Andrew > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of > the individual(s) named above and further non-explicilty authorized > disclosure, copying, distribution or use of the contents of this > information, even if partially, including attached files, is strictly > prohibited and will be considered a criminal offense. If you are not the > intended recipient be aware that any disclosure, copying, distribution or > use of the contents of this information, even if partially, including > attached files, is strictly prohibited, will be considered a criminal > offense, so you must reply to the original sender to inform about this > communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Tue Oct 14 20:38:48 2025 From: sami.salih at outlook.com (Sami Salih) Date: Tue, 14 Oct 2025 20:38:48 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> Message-ID: Speaking from a nation currently enduring military conflict and the near-total destruction of its infrastructure. At this moment?and for the foreseeable future?progress is impossible. We respectfully ask that our share of the resources be reserved until we are able to address and overcome our most urgent crisis. Sent from Outlook for Android ________________________________ From: Noah Sent: Tuesday, October 14, 2025 8:33:55 PM To: Sami Salih Cc: Jordi Palet Martinez ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate On Tue, 14 Oct 2025, 8:10?pm Sami Salih, > wrote: That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. A classic example in contemporary african history is states that suffered prolonged civil wars such as Somalia, South Sudan, Burundi, Sierra Leon to name but a few whose pacification is as recent as a decade ago with some sense of peace & political stability starting to emerge. On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. 100% and this is the sorf of foresight that most actors both within Afrinic and the internet community does not seem to grasp. If we can reserve space for critical Infra such as IXP's then policy development should always be guided by a considerable number of socio-economic factors. Mwalimu Nyerere once stated to the nation that, look, those minerals that we cant exploit today, can always be exploited later in futute when posterity is ready and knowledgable enough to make good sense of them after all, they dont expire. Its now 5 decades later and with education, information and exposure, the people are now able to use the raw-material and build industry locally. Foresight my people, foresight. We are internet engineers yes but we must think beyond just engineering. Noah Sami Salih, Sent from Outlook for Android ________________________________ From: jordi.palet--- via RPD > Sent: Tuesday, October 14, 2025 7:06:14 PM To: RPD > Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet El 14 oct 2025, a las 17:14, Owen DeLong > escribi?: If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen On Oct 14, 2025, at 02:05, jordi.palet--- via RPD > wrote: ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet El 14 oct 2025, a las 10:46, Owen DeLong via RPD > escribi?: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen On Oct 14, 2025, at 01:22, Hendrik Visage > wrote: ? Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Tue Oct 14 20:52:19 2025 From: sami.salih at outlook.com (Sami Salih) Date: Tue, 14 Oct 2025 20:52:19 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> Message-ID: Seun, the term "indefinitely" carries a lot of weight, and its meaning can vary greatly depending on context and background. That?s why it?s essential for us to clearly define this period in a way that truly serves African interests and reflects the will of our people. The perspective you mentioned is a valid example of that need. In our case, most of the major players have already received the necessary know-how, resources, and demonstrated the willingness to deploy IPv6. I believe that any further assignments of IPv4 resources will likely be transferred outside the region to support easier investment. Unfortunately, it?s unlikely that the current generation will truly benefit from these IPs in the long run, at least in my home country. Sami Salih. Sent from Outlook for Android ________________________________ From: Seun Ojedeji Sent: Tuesday, October 14, 2025 9:08:02 PM To: Sami Salih Cc: Jordi Palet Martinez ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Good points Sami, but I am not a fan of leaving it indefinitely, that will make it become useless to generation to come nor will it be useful for present generation. So long as there are legitimate need/use for v4 at the moment, it make sense at some point in the near future to use the reserve. This can be through tieing allocation to a more intentional or aggressive V6 deployment requirements. A policy that makes v4 to be an add-on to V6 allocation/deployment may be a good use of the reserved space. Otherwise the future generation which will be more V6 aware/exposed than you and I may not find so many use cases for v4 at their time. Regards ---- Sent from my mobile kindly excuse typos On Tue, 14 Oct 2025, 11:59?am Sami Salih, > wrote: That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. Sami Salih, Sent from Outlook for Android ________________________________ From: jordi.palet--- via RPD > Sent: Tuesday, October 14, 2025 7:06:14 PM To: RPD > Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet El 14 oct 2025, a las 17:14, Owen DeLong > escribi?: If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen On Oct 14, 2025, at 02:05, jordi.palet--- via RPD > wrote: ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet El 14 oct 2025, a las 10:46, Owen DeLong via RPD > escribi?: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen On Oct 14, 2025, at 01:22, Hendrik Visage > wrote: ? Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 22:48:10 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 15:48:10 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: <6069334D-FD3C-4BC4-B945-273059F3CA4D@delong.com> I guess that entirely depends on the policies they set for their ISPs and the extent to which they provide IPv4AAS gateways to get to their IPv6 infrastructure. Owen > On Oct 14, 2025, at 02:55, wrote: > > Owen, > Will that not exclude many of their their citizens from accessing digital services? > > > > From: Owen DeLong > Sent: 14 October 2025 11:44 > To: Noah > Cc: Ben Roberts AfriNIC ; Andrew Alston ; RPD > Subject: Re: [rpd] Questions about IP Allocation rate > > Or better yet, not reserving IPv4 could spur those governments to deploy their govnets on IPv6 from the beginning with a clean greenfield design leapfrogging past the legacy baggage inherent in any IPv4 based solution. > > Owen > > > >> On Oct 13, 2025, at 12:26, Noah > wrote: >> >> ? >> Ben >> >> There is critical structural challenge in the continents digital landscape and you more than anyone knows this very well that we also suffer from uneven maturity of Digital Public Infrastructure and Government Networks (GovNet), which directly impacts the equitable deployment of essential digital services across majority of countries across our continent. >> >> Look we are talking about numbering infrastructure that would support services like e-government, digital IDs, and public/private data exchanges, while aligning with AFRINIC's exhaustion-phase policies. >> >> We can not shy away from these reality or pretend that there is lack of foresight from actors at Afrinic and the community at large. >> >> Its a known fact that many of our African governments lack operational GovNets and strategic reservations of IPv4 address space from AFRINIC could serve as a targeted incentive to bridge these gaps. >> >> >> >> Cheers, >> ./noah >> >> >> On Mon, 13 Oct 2025, 8:34?pm Ben Roberts - AfriNIC, > wrote: >>> I think The DPI systems are normally run by state owned digital agency entities which are already mostly LIRs having some space. It is not quite as you describe being state owned LIRs that have sovereign owned IPs that are independent of LIRs.. >>> >>> >>> >>> Sent from my iPhone >>> >>> >>>> On 13 Oct 2025, at 20:01, Noah > wrote: >>>> >>>> ? >>>> 54 African States are taking public services online. >>>> >>>> Digital Public infrastructure (DPI) is nolonger an idea. Its a real thing. DPI is critical. The private sector will tap into that infrastructure. Its here now. >>>> >>>> Each of the 54 African states need address space indepedent of LIR space in each sovereign state. >>>> >>>> These are not ideas that actors in the private sector care about or think about. >>>> >>>> Cheers, >>>> ./noah >>>> >>>> >>>> On Mon, 13 Oct 2025, 5:52?pm Andrew Alston, > wrote: >>>>> Hi All, >>>>> >>>>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>>>> >>>>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>>>> >>>>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>>>> >>>>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>>>> >>>>> Thanks >>>>> >>>>> Andrew >>>>> >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 22:50:25 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 15:50:25 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: <22BC6750-0939-4876-B430-56DD77219CDD@delong.com> > On Oct 14, 2025, at 03:01, Andrew Alston wrote: > > Not Necessarily Ben. > > Reality is they could back end Government Networks with V6 and front the services with V4 which map to the V6 backend. > > This would substantially reduce the amount of IPv4 space actually needed by the governments, and provide dual-stack from the start. I have serious doubts that you will find governments in Africa requiring external access to more than 200+ unique services (which would represent a single /24 on the front end). Potentially even less with SNI and some creativity. > We also need to keep in mind that many government services are now hosted behind the likes of CloudFlare - specifically for DDoS prevention mechanisms - and I'm not sure that IPv4 allocations by government entities are necessarily a good indicator of digital migration, since these services are not hosted on IPv4 space allocated to those entities. The same applies to services hosted in any of the major cloud providers. Also a good point. And I know that Akamai and Cloudflare are both capable of providing dual-stack front ends to IPv6-only content. Owen From owen at delong.com Tue Oct 14 22:53:32 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 15:53:32 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> Message-ID: <26B4C34E-836A-4CF0-9962-22F360659DEA@delong.com> Could we, perhaps, separate the statistics accordingly and call them: a) Reserved b) Reclaimed->Quarantine c) Returned->Quarantine d) I view this as a pathological case of b. Frankly, I wouldn?t mind seeing b,c,d combined even, but presumably there is a lifespan to the quarantines in question whereas the ones in category a (truly Reserved) are reserved until consumed by their reserved purpose or policy changes, so conflating them all as Reserved seems misleading. Owen > On Oct 14, 2025, at 06:26, Madhvi Gokool via RPD wrote: > > Dear Andrew > > The status 'Reserved' is provided to the following cases :- > > a) Resources that are reserved according to ratified and implemented policies(one /12 IPv4 under the soft landing policy and 2 x 16?s IPv4 prefixes and small ASNs for IXPs) > > b) Resources that have been reclaimed from organisations during the closure exercises and quarantined > > c) Resources that have been voluntarily returned by resource members and quarantined > > Quarantined resources in the case of b) and c) above are subject to a cleanup process to ensure sanity before they are added to the available pool of resources. > > d) Resources that have been deregistered from the AFRINIC whois database after the investigation of misappropriated resources were also quarantined. > > We will produce a breakdown of these reservations by tomorrow. > > Regards > > Madhvi > > > > On 14/10/2025 13:11, Andrew Alston wrote: >> Hi Madhvi, >> >> I'm a little confused by the stats on that page. According to the CPM AfriNIC currently reserves as a /16 for IXP space and a /12 under soft landing. This accounts for a total of 1,114,112 addresses. >> >> The stats page shows total reservations of 17509 /24s - which amounts to roughly a /10 and another /14 in reserved space. This is more than 4 times the amount of reserved space that I can account for in the CPM - so what is the rest of it and what am I missing here? >> >> Thanks >> >> Andrew >> >> >> On Tue, Oct 14, 2025 at 11:03?AM Madhvi Gokool via RPD > wrote: >>> Dear Sir >>> AFRINIC publishes statistics here - https://stats.afrinic.net >>> The graph titled ?Distribution of IPv4 (/24) per year? on the page Statistics Portal can be referenced for yearly distribution, In addition, The ?Filter by date Range? can be used to get granular statistics for the IPv4 allocations. >>> We also wish to inform you that while the page is accessible on Firefox and Safari browsers, we have noticed an erratic behaviour when accessed via Chrome browser. We are investigating this erratic behaviour at the moment. >>> Kind Regards >>> Madhvi Gokool >>> AFRINIC Policy Liaison >>> >>> >>> On 13/10/2025 18:43, Andrew Alston wrote: >>>> Hi All, >>>> >>>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>>> >>>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>>> >>>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>>> >>>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>>> >>>> Thanks >>>> >>>> Andrew >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 22:55:13 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 15:55:13 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> Message-ID: <1384F040-3341-4150-BF16-EC97F7589B86@delong.com> > On Oct 14, 2025, at 04:41, Noah wrote: > > > > > On Tue, 14 Oct 2025, 1:56?pm Andrew Alston, > wrote: >> Any government who is doing DPI needs to wake up and get a reality check. > > > DPI as in Digital Public Infrastructure (egovt, digital-id, govnet, etc) > Any government that expects to do this DPI on IPv4 needs to wake up and get a reality check. >> >> deep packet inspection is as good as dead. > > > Not that DPI bro... LoL? I would hope. Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Tue Oct 14 22:59:04 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 15:59:04 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> Message-ID: > On Oct 14, 2025, at 04:38, Noah wrote: > > > > > On Tue, 14 Oct 2025, 1:46?pm jordi.palet--- via RPD, > wrote: >> >> In both cases you need ?some? IPv4 addresses, and because you can?t route less than /24, most of the time, you will use a /24. > > > This is a very important point. At bare minimum, that is the block folks want to see in the DFZ. Fine, let?s reserve a single /24 for each of the governments that doesn?t currently have one and move on. Keeping a /12 is insane. >> If you have multiple PoPs for your BGP upstreams, then you may need multiple /24s. > > > That is why we settled for /22 in the softlanding policy. THere?s no need for IPv4 to interface with BGP upstreams? IPv4 routing across IPv6 BGP sessions works perfectly well and is not difficult to configure on Juniper, Cisco, FRR, Arista. Other platforms are likely similarly easy to configure, I just haven?t played with them for this purpose. IPv4 Link Local peering is also a perfectly viable solution. Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Wed Oct 15 00:09:21 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 17:09:21 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <173501dc3cf0$b595c020$20c14060$@afrinic.net> References: <173501dc3cf0$b595c020$20c14060$@afrinic.net> Message-ID: <25847EF6-AB2A-46F7-BFF0-922F1AF72ACA@delong.com> An HTML attachment was scrubbed... URL: From owen at delong.com Wed Oct 15 00:30:48 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 17:30:48 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From owen at delong.com Wed Oct 15 00:34:02 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 17:34:02 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: <451D1439-EB09-4ACD-8385-D4D9ED57D798@delong.com> An HTML attachment was scrubbed... URL: From omo.oaiya at wacren.net Wed Oct 15 04:36:34 2025 From: omo.oaiya at wacren.net (Omo Oaiya) Date: Wed, 15 Oct 2025 05:36:34 +0100 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <44830741-6C2C-44D5-BBBA-369ACCF19838@yahoo.fr> References: <5DF5ED45-A4B2-4DEB-B279-A7C045495500@wacren.net> <44830741-6C2C-44D5-BBBA-369ACCF19838@yahoo.fr> Message-ID: <99B4F6C3-E7C5-473C-AFE2-B2042FB00F90@wacren.net> Correct...civility and focus are essential. If our policies are to reflect African realities, we need stronger input from those actually building and running networks across the continent. It?s less about becoming an IG forum and more about grounding our work in Africa?s operational context to ensure the process truly serves the region. Let?s keep it practical and focused on that goal. > On 14 Oct 2025, at 14:46, Gr?goire EHOUMI wrote: > > Hello, > >> On Oct 12, 2025, at 6:31?AM, Omo Oaiya via RPD wrote: >> >> ? >> It?s great to see discussion back on the list, a good sign that the community spirit is still strong. I agree with Owen. What really matters is that the feedback loop stays open, clear, and timely. >> >> On Ben?s point, participation will grow if we make the PDP more inclusive and relevant. We should bring in people from IXPs, NRENs, academia, civil society, and sectors shaping Africa?s digital economy. Linking policy work to that wider digital transformation agenda will draw new energy and perspectives. >> >> Let?s keep it going. >> >> Best, >> Omo >> > ?More inclusive? by offering a pleasant, productive PDP to the expected standards, right ? > > Policy discussions and meetings have always been open to anyone to join and participate. No one has been prevented from participating in pdp, except perhaps our behaviours may have discouraged, scared away many people in our diverse and fragile ecosystem. > > The board made a key prerequisite to resumption of PDP as below: > "A key prerequisite will be to ensure that all community mailing lists maintain an atmosphere of civility and constructive engagement." > > Governments are more attentive now, watching and assessing us. > It shouldn't be like before thanks for our collective efforts. > > ?More relevant? yes towards policy making for Number resources management, but without turning the PDP into an IG forum? Community, members, board and staff should make sure that policies we discuss and approve serve the interests AFRICA and not private, personal interests. > > Cheers, > - > Gr?goire > Omo OAIYA Chief Strategy Officer/Directeur de la Strat?gie | WACREN m: +234 808 888 1571 , +233 536 269 987 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Wed Oct 15 05:13:09 2025 From: sami.salih at outlook.com (Sami Salih) Date: Wed, 15 Oct 2025 05:13:09 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: We cannot guarantee that any reserved portion of the IPv4 space will remain "fair" in an unforeseen future?simply because the future is, by nature, unpredictable. That said, from my perspective, the currently assigned/allocated space is sufficient for now and the near future. Businesses with growing needs can adopt IPv6, using their existing IPv4 resources to support the migration/transition. For new entrants, we can consider providing small allocations of IPv4, but only after carefully verifying that they are legitimate African businesses. Sami Salih. Sent from Outlook for Android ________________________________ From: Owen DeLong Sent: Wednesday, October 15, 2025 3:30:48 AM To: Sami Salih Cc: Noah ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate How do you propose that share be measured? Owen On Oct 14, 2025, at 15:38, Sami Salih wrote: ? Speaking from a nation currently enduring military conflict and the near-total destruction of its infrastructure. At this moment?and for the foreseeable future?progress is impossible. We respectfully ask that our share of the resources be reserved until we are able to address and overcome our most urgent crisis. Sent from Outlook for Android ________________________________ From: Noah Sent: Tuesday, October 14, 2025 8:33:55 PM To: Sami Salih Cc: Jordi Palet Martinez ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate On Tue, 14 Oct 2025, 8:10?pm Sami Salih, > wrote: That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. A classic example in contemporary african history is states that suffered prolonged civil wars such as Somalia, South Sudan, Burundi, Sierra Leon to name but a few whose pacification is as recent as a decade ago with some sense of peace & political stability starting to emerge. On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. 100% and this is the sorf of foresight that most actors both within Afrinic and the internet community does not seem to grasp. If we can reserve space for critical Infra such as IXP's then policy development should always be guided by a considerable number of socio-economic factors. Mwalimu Nyerere once stated to the nation that, look, those minerals that we cant exploit today, can always be exploited later in futute when posterity is ready and knowledgable enough to make good sense of them after all, they dont expire. Its now 5 decades later and with education, information and exposure, the people are now able to use the raw-material and build industry locally. Foresight my people, foresight. We are internet engineers yes but we must think beyond just engineering. Noah Sami Salih, Sent from Outlook for Android ________________________________ From: jordi.palet--- via RPD > Sent: Tuesday, October 14, 2025 7:06:14 PM To: RPD > Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet El 14 oct 2025, a las 17:14, Owen DeLong > escribi?: If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen On Oct 14, 2025, at 02:05, jordi.palet--- via RPD > wrote: ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet El 14 oct 2025, a las 10:46, Owen DeLong via RPD > escribi?: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen On Oct 14, 2025, at 01:22, Hendrik Visage > wrote: ? Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston > wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Wed Oct 15 05:20:36 2025 From: sami.salih at outlook.com (Sami Salih) Date: Wed, 15 Oct 2025 05:20:36 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <451D1439-EB09-4ACD-8385-D4D9ED57D798@delong.com> References: <451D1439-EB09-4ACD-8385-D4D9ED57D798@delong.com> Message-ID: No, Owen If we can ensure that " present needs are actual" we wouldn't be having this debate. The moment unnecessary IPv4 space is assigned to a business, they will quickly monetize it through resource transfers. ________________________________ From: Owen DeLong Sent: Wednesday, October 15, 2025 3:34:38 am To: Sami Salih Cc: jordi.palet at consulintel.es ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Remember, whatever you put on hold to protect future generations from significant scarcity subjects current generations to equivalent scarcity. The difference is that the future need is theoretical and the present needs are actual. Owen On Oct 14, 2025, at 15:39, Sami Salih wrote: ? That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. Sami Salih, Sent from Outlook for Android ________________________________ From: jordi.palet--- via RPD Sent: Tuesday, October 14, 2025 7:06:14 PM To: RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet El 14 oct 2025, a las 17:14, Owen DeLong escribi?: If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen On Oct 14, 2025, at 01:22, Hendrik Visage wrote: ? Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Wed Oct 15 05:39:00 2025 From: owen at delong.com (Owen DeLong) Date: Tue, 14 Oct 2025 22:39:00 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: An HTML attachment was scrubbed... URL: From omo.oaiya at wacren.net Wed Oct 15 06:25:26 2025 From: omo.oaiya at wacren.net (Omo Oaiya) Date: Wed, 15 Oct 2025 07:25:26 +0100 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: <590FB2C9-DFBC-4F42-9EEF-6BE92F46D834@wacren.net> AFRINIC staff operate within community-defined policies, and if there are weaknesses, it is our collective responsibility to improve the framework, not question integrity. We need to keep this discussion grounded in Africa?s own realities, not global precedents. Policy should reflect the conditions under which African networks grow. With our varied governance and market environments, balanced and deliberate stewardship of the remaining IPv4 space is key to sustainable progress. > On 15 Oct 2025, at 06:39, Owen DeLong via RPD wrote: > > That assumes a great many facts not in evidence and basically accuses every current applicant of fraud. It also calls into question the quality of the job done by the AFRINIC staff. If that?s truly an issue at the moment, then we should address the staff problems and correct those issues, but assuming that every applicant is a fraud is NOT a valid basis for policy. > > > Owe > > >> On Oct 14, 2025, at 22:20, Sami Salih wrote: >> >> ? >> No, Owen >> If we can ensure that " present needs are actual" we wouldn't be having this debate. >> >> The moment unnecessary IPv4 space is assigned to a business, they will quickly monetize it through resource transfers. >> >> From: Owen DeLong >> Sent: Wednesday, October 15, 2025 3:34:38 am >> To: Sami Salih >> Cc: jordi.palet at consulintel.es ; RPD >> Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate >> >> Remember, whatever you put on hold to protect future generations from significant scarcity subjects current generations to equivalent scarcity. The difference is that the future need is theoretical and the present needs are actual. >> >> Owen >> >> >> On Oct 14, 2025, at 15:39, Sami Salih wrote: >> >> ? >> That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. >> On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. >> >> Sami Salih, >> >> >> Sent from Outlook for Android >> From: jordi.palet--- via RPD >> Sent: Tuesday, October 14, 2025 7:06:14 PM >> To: RPD >> Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate >> >> I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. >> >> Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. >> >> Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. >> >> I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >> El 14 oct 2025, a las 17:14, Owen DeLong escribi?: >> >> If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. >> >> Owen >> >> >> On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: >> >> ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. >> >> Regards, >> Jordi >> >> @jordipalet >> >> >> El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: >> >> Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. >> >> Owen >> >> >> On Oct 14, 2025, at 01:22, Hendrik Visage wrote: >> >> ? Question: >> >> Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? >> >> ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. >> >> Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" >> >> --- >> Hendrik Visage >> Instant messaging: https://t.me/hvisage >> >> >> On 13 Oct 2025, at 16:43, Andrew Alston wrote: >> >> Hi All, >> >> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >> >> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >> >> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >> >> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >> >> Thanks >> >> Andrew >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> --- >> >> Hendrik Visage >> >> hvisage at hevis.co.za >> >> >> HeViS.Co Systems Pty Ltd >> >> https://www.envisage.co.za >> >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Wed Oct 15 06:31:05 2025 From: sami.salih at outlook.com (Sami Salih) Date: Wed, 15 Oct 2025 06:31:05 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: It?s not about the staff ? they are doing an excellent job, indeed. The issue lies in the broader structural situation in many of our countries. Looking at the statistics shared in yhis list earlier, it becomes obvious that what is labelled as the ?top 10? are not in fact the top African businesses when it comes to using v$ resources. Sent from Outlook for Android ________________________________ From: Owen DeLong Sent: Wednesday, October 15, 2025 8:39:00 AM To: Sami Salih Cc: jordi.palet at consulintel.es ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate That assumes a great many facts not in evidence and basically accuses every current applicant of fraud. It also calls into question the quality of the job done by the AFRINIC staff. If that?s truly an issue at the moment, then we should address the staff problems and correct those issues, but assuming that every applicant is a fraud is NOT a valid basis for policy. Owe On Oct 14, 2025, at 22:20, Sami Salih wrote: ? No, Owen If we can ensure that " present needs are actual" we wouldn't be having this debate. The moment unnecessary IPv4 space is assigned to a business, they will quickly monetize it through resource transfers. ________________________________ From: Owen DeLong Sent: Wednesday, October 15, 2025 3:34:38 am To: Sami Salih Cc: jordi.palet at consulintel.es ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Remember, whatever you put on hold to protect future generations from significant scarcity subjects current generations to equivalent scarcity. The difference is that the future need is theoretical and the present needs are actual. Owen On Oct 14, 2025, at 15:39, Sami Salih wrote: ? That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. Sami Salih, Sent from Outlook for Android ________________________________ From: jordi.palet--- via RPD Sent: Tuesday, October 14, 2025 7:06:14 PM To: RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet El 14 oct 2025, a las 17:14, Owen DeLong escribi?: If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen On Oct 14, 2025, at 01:22, Hendrik Visage wrote: ? Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Wed Oct 15 06:33:29 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Wed, 15 Oct 2025 08:33:29 +0200 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> Message-ID: Is not for the peering (it is not needed even for IXPs, we can use IPv6-only), is for the NAT64. Saludos, Jordi @jordipalet > El 15 oct 2025, a las 0:59, Owen DeLong escribi?: > > > >> On Oct 14, 2025, at 04:38, Noah wrote: >> >> >> >> >> On Tue, 14 Oct 2025, 1:46?pm jordi.palet--- via RPD, > wrote: >>> >>> In both cases you need ?some? IPv4 addresses, and because you can?t route less than /24, most of the time, you will use a /24. >> >> >> This is a very important point. At bare minimum, that is the block folks want to see in the DFZ. > > Fine, let?s reserve a single /24 for each of the governments that doesn?t currently have one and move on. Keeping a /12 is insane. > >>> If you have multiple PoPs for your BGP upstreams, then you may need multiple /24s. >> >> >> That is why we settled for /22 in the softlanding policy. > > THere?s no need for IPv4 to interface with BGP upstreams? IPv4 routing across IPv6 BGP sessions works perfectly well and is not difficult to configure on Juniper, Cisco, FRR, Arista. Other platforms are likely similarly easy to configure, I just haven?t played with them for this purpose. > > IPv4 Link Local peering is also a perfectly viable solution. > > Owen > > ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Wed Oct 15 06:40:20 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Wed, 15 Oct 2025 08:40:20 +0200 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <05CA3C8D-446F-46F4-918E-7252192684F6@consulintel.es> <851EFCCB-889A-4A77-A4E3-E0A91F4FD452@delong.com> <470826D1-8ECB-42FC-AB6D-F1A3A3842A49@consulintel.es> Message-ID: <1267ED37-D982-41EF-9B86-7C8550456299@consulintel.es> Exactly. I don?t think we must keep holding some resources forever. It hasn?t been done in any other region and it is working out sufficiently well. Instead we need to ensure that the reserved space are only available for new entrants, maximum a /22. Then we also need policies that allow transfers and policies that allow leasing of small blocks, so small organisations and goverments organizations that don?t have any resource now can start their IPv6 deployment with a minimum block of IPv4. Regards, Jordi @jordipalet > El 14 oct 2025, a las 20:08, Seun Ojedeji escribi?: > > Good points Sami, but I am not a fan of leaving it indefinitely, that will make it become useless to generation to come nor will it be useful for present generation. > > So long as there are legitimate need/use for v4 at the moment, it make sense at some point in the near future to use the reserve. This can be through tieing allocation to a more intentional or aggressive V6 deployment requirements. > > A policy that makes v4 to be an add-on to V6 allocation/deployment may be a good use of the reserved space. Otherwise the future generation which will be more V6 aware/exposed than you and I may not find so many use cases for v4 at their time. > > Regards > ---- > Sent from my mobile > kindly excuse typos > > On Tue, 14 Oct 2025, 11:59?am Sami Salih, > wrote: >> That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. >> On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. >> >> Sami Salih, >> >> >> Sent from Outlook for Android >> From: jordi.palet--- via RPD > >> Sent: Tuesday, October 14, 2025 7:06:14 PM >> To: RPD > >> Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate >> >> I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. >> >> Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. >> >> Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. >> >> I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... >> >> Saludos, >> Jordi >> >> @jordipalet >> >> >>> El 14 oct 2025, a las 17:14, Owen DeLong > escribi?: >>> >>> If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. >>> >>> Owen >>> >>> >>>> On Oct 14, 2025, at 02:05, jordi.palet--- via RPD > wrote: >>>> >>>> ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. >>>> >>>> Regards, >>>> Jordi >>>> >>>> @jordipalet >>>> >>>> >>>>> El 14 oct 2025, a las 10:46, Owen DeLong via RPD > escribi?: >>>>> >>>>> Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. >>>>> >>>>> Owen >>>>> >>>>> >>>>>> On Oct 14, 2025, at 01:22, Hendrik Visage > wrote: >>>>>> >>>>>> ? Question: >>>>>> >>>>>> Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? >>>>>> >>>>>> ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. >>>>>> >>>>>> Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" >>>>>> >>>>>> --- >>>>>> Hendrik Visage >>>>>> Instant messaging: https://t.me/hvisage >>>>>> >>>>>> >>>>>>> On 13 Oct 2025, at 16:43, Andrew Alston > wrote: >>>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>>>>>> >>>>>>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>>>>>> >>>>>>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>>>>>> >>>>>>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Andrew >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> RPD mailing list >>>>>>> RPD at afrinic.net >>>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>>> >>>>>> --- >>>>>> >>>>>> Hendrik Visage >>>>>> >>>>>> hvisage at hevis.co.za >>>>>> >>>>>> HeViS.Co Systems Pty Ltd >>>>>> >>>>>> https://www.envisage.co.za >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> RPD mailing list >>>>>> RPD at afrinic.net >>>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> >>>> ********************************************** >>>> IPv4 is over >>>> Are you ready for the new Internet ? >>>> http://www.theipv6company.com >>>> The IPv6 Company >>>> >>>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> >> ********************************************** >> IPv4 is over >> Are you ready for the new Internet ? >> http://www.theipv6company.com >> The IPv6 Company >> >> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1mgirlieadezpet at gmail.com Wed Oct 15 07:29:13 2025 From: 1mgirlieadezpet at gmail.com (1mgirlieadezpet at gmail.com) Date: Wed, 15 Oct 2025 07:29:13 +0000 (UTC) Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: <499274612.1686408.1760513353413@mail.yahoo.com> Hi everyone,I personally support a partial release of the /12 reserved space. While it?s important to keep some addresses for critical infrastructure and new entrants (as Fernando highlighted), we should also acknowledge that after more than a decade, it?s reasonable to reassess how much of that space truly needs to remain reserved. A partial release would help meet current demand, reduce risks of hijacking or underutilization, and still preserve enough space for future or unforeseen needs. In my opinion, I suggest we: 1. Carry out an actual review of IPv4 usage and demand trends in the region,2. Clearly define criteria for what portion stays reserved, and?3. Periodically re-evaluate as the Internet landscape evolves. This approach tends to keep things fair, flexible, and future-focused? aligning with AFRINIC?s goal of inclusive Internet growth across Africa. Best regards,Adepetun Oluwaseun Ibukun?Principal System Analyst?Federal University of Lafia?Nigeria Yahoo Mail: Search, Organize, Conquer On Mon, Oct 13, 2025 at 4:54 PM, Fernando Frediani wrote: Hi Allocating resources for Future Use is commonly important when you can't predict things in long term and think it was a good decision taken in the past. Same thing for Critical Infrastructure Resources reservation that most RIRs have. They have a clear reason to exist and be treated as such. If we, as a Community, are going to discuss allocation of remaining reserved resources I firmly believe this should be done with enough time to analyze the current IPv4 exhaustion, demand in the region and how it can benefit most organization in Africa. A /12 may be a lot but don't be surprised how fast that can go. Therefore we should have as basis some fundamental restrictions in order to make sure these resources go to those willing to build Internet Infrastructure AND (this and is important) that currently have no chances to get much IPv4 space. I am talking about newcomers. In order for them to exist and start building something they need some minimal space, get at cruising speed and be more independent from there. Those who already have some allocations are more likely to have revenue to transfer further blocks as required. The current /22 limitation well tested in other RIRs and provides a reasonable minimal amount of IPv4 to start with. This favors the emergence of a greater number of organizations that build Internet Infrastructure in the region, which is always positive for greater competitiveness and innovation in this ecosystem. Best regards Fernando Frediani On 10/13/2025 11:43 AM, Andrew Alston wrote: > Hi All, > > I was wondering if there were updated statistics for the amount of > space allocated in the last 3 years.? In addition to this information > regarding exactly how much free space is still available in the IPv4 > unallocated pool (excluding reservations) > > I ask this because depending on the allocation rate - we may wish to > consider revising the soft-landing policy that currently reserves a > /12 worth of ipv4 space for "future uses, as yet unforeseen". > > I point out that the soft landing policy was ratified in 2011, and if > we still, after 14 years, have not been able to articulate a clear > reason for such a large reservation, I think it's time we look at > most, if not all, of that /12 back into the main unallocated pool that > can be allocated for African resource holders that actually need it. > > Amongst other reasons, sitting with unallocated, unannounced, reserved > space like this leaves the space vulnerable to hijacking and malicious > use or even potential theft. > > Thanks > > Andrew > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Wed Oct 15 07:37:45 2025 From: noah at neo.co.tz (Noah) Date: Wed, 15 Oct 2025 10:37:45 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <5FBD19DD-E36D-4DDB-B2AB-21C91850B3A0@delong.com> <172801dc3cf0$9f9ff470$dedfdd50$@afrinic.net> <80580769-B9B1-4D44-AF70-1EDD53D8DA9E@hevis.co.za> Message-ID: On Wed, 15 Oct 2025, 9:42?am jordi.palet--- via RPD, wrote: > Is not for the peering (it is not needed even for IXPs, we can use > IPv6-only), is for the NAT64. > RFC6146 is widely supported by most vendors today and a bare minimum of /24 v4 space for translators is foresight grounded on reality of v4/v6 co-existance. More so for new entrants who must not be succummed to IPv$ brokers/leasers who stockpile to monetize in future based on scarcity. Noah Noah -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Wed Oct 15 08:43:35 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Wed, 15 Oct 2025 11:43:35 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: <1cf17ffd-f0db-4afd-ab67-8f92d79b5a46@afrinic.net> Message-ID: Just an update here, I've now written some (admittedly ugly) code to parse the full bgp table for announced routes in such a way that it can be used for high speed comparison against a list of supplied "reserved" ranges to ensure that that none of these are appearing in the DFZ - and if they are what ASN's are originating the data. As soon as AfriNIC supplies the full list of reserved ranges I will be able to supply a list of any address space currently showing up that shouldn't be if any. If AfriNIC were to publish the full list of reserved ranges somewhere that it could be easily fetched - it would be a simple thing to run this code against a BGP feed once a day against an updated reserved list and then send an automated alert should reserved ranges be showing up in the BGP table, along with who is announcing these routes. I think this would be a worthwhile exercise to prevent any hijacking or theft of space. (Note the code I used parses specifically against a dump of the BGP table as taken from a Juniper router so its rather junos specific, and of course needs the further code added to do the comparison against reserved space. Once AfriNIC releases the full list of reserved ranges or gives an indication where such a list can be downloaded as it is updated (which would be ideal) I will finalize the code to do the comparison and would be happy to release it publically) Thanks Andrew On Tue, Oct 14, 2025 at 4:45?PM Andrew Alston wrote: > Can you also please supply the ranges so that a BGP table audit can be > done to ensure that these resources are indeed not being used > inappropriately or illegally please. > > Andrew > > On Tue, 14 Oct 2025 at 16:27, Madhvi Gokool via RPD > wrote: > >> Dear Andrew >> >> The status 'Reserved' is provided to the following cases :- >> >> a) Resources that are reserved according to ratified and implemented >> policies(one /12 IPv4 under the soft landing policy and 2 x 16?s IPv4 >> prefixes and small ASNs for IXPs) >> >> b) Resources that have been reclaimed from organisations during the >> closure exercises and quarantined >> >> c) Resources that have been voluntarily returned by resource members >> and quarantined >> >> Quarantined resources in the case of b) and c) above are subject to a >> cleanup process to ensure sanity before they are added to the available >> pool of resources. >> >> d) Resources that have been deregistered from the AFRINIC whois database >> after the investigation of misappropriated resources were also quarantined. >> >> We will produce a breakdown of these reservations by tomorrow. >> >> Regards >> >> Madhvi >> >> >> On 14/10/2025 13:11, Andrew Alston wrote: >> >> Hi Madhvi, >> >> I'm a little confused by the stats on that page. According to the CPM >> AfriNIC currently reserves as a /16 for IXP space and a /12 under soft >> landing. This accounts for a total of 1,114,112 addresses. >> >> The stats page shows total reservations of 17509 /24s - which amounts to >> roughly a /10 and another /14 in reserved space. This is more than 4 times >> the amount of reserved space that I can account for in the CPM - so what is >> the rest of it and what am I missing here? >> >> Thanks >> >> Andrew >> >> >> On Tue, Oct 14, 2025 at 11:03?AM Madhvi Gokool via RPD >> wrote: >> >>> Dear Sir >>> >>> AFRINIC publishes statistics here - https://stats.afrinic.net >>> >>> The graph titled ?Distribution of IPv4 (/24) per year? on the page Statistics >>> Portal can be referenced for yearly >>> distribution, In addition, The ?Filter by date Range? can be used to get >>> granular statistics for the IPv4 allocations. >>> >>> We also wish to inform you that while the page is accessible on Firefox >>> and Safari browsers, we have noticed an erratic behaviour when accessed via >>> Chrome browser. We are investigating this erratic behaviour at the moment. >>> >>> Kind Regards >>> >>> Madhvi Gokool >>> >>> AFRINIC Policy Liaison >>> >>> >>> On 13/10/2025 18:43, Andrew Alston wrote: >>> >>> Hi All, >>> >>> I was wondering if there were updated statistics for the amount of space >>> allocated in the last 3 years. In addition to this information regarding >>> exactly how much free space is still available in the IPv4 unallocated pool >>> (excluding reservations) >>> >>> I ask this because depending on the allocation rate - we may wish to >>> consider revising the soft-landing policy that currently reserves a /12 >>> worth of ipv4 space for "future uses, as yet unforeseen". >>> >>> I point out that the soft landing policy was ratified in 2011, and if we >>> still, after 14 years, have not been able to articulate a clear reason for >>> such a large reservation, I think it's time we look at most, if not all, of >>> that /12 back into the main unallocated pool that can be allocated for >>> African resource holders that actually need it. >>> >>> Amongst other reasons, sitting with unallocated, unannounced, reserved >>> space like this leaves the space vulnerable to hijacking and malicious use >>> or even potential theft. >>> >>> Thanks >>> >>> Andrew >>> >>> >>> >>> _______________________________________________ >>> RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Wed Oct 15 08:58:12 2025 From: owen at delong.com (Owen DeLong) Date: Wed, 15 Oct 2025 01:58:12 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: <3C3C3E6F-48C4-488D-8937-3E566E8ED9FB@delong.com> An HTML attachment was scrubbed... URL: From owen at delong.com Wed Oct 15 08:54:41 2025 From: owen at delong.com (Owen DeLong) Date: Wed, 15 Oct 2025 01:54:41 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: References: Message-ID: <8EA222C4-FAA9-4228-8E54-6CC98830D271@delong.com> An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Wed Oct 15 10:51:58 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Wed, 15 Oct 2025 13:51:58 +0300 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <8EA222C4-FAA9-4228-8E54-6CC98830D271@delong.com> References: <8EA222C4-FAA9-4228-8E54-6CC98830D271@delong.com> Message-ID: <026901dc3dc1$bbed8440$33c88cc0$@afrinic.net> Owen, South Africa has approx 850 AS Numbers with approx 64 million population which is 0.00001328125 members per capita of population. The whole of Africa has population of say 1.5 Billion. If the continental average were to catch up with South Africa, arguably the most digitally advanced African Nation then one can apply that average x the pan African population to get 0.00001328125 x 1.5 Billion = 19,921 members So an increase from 2400 number holding resource members to 19,921, so yes exactly about 17,000 extra members are possible. Each one holding AS number, a nominal IPv4 range, plus a bigger IPv6 range. While some African nations are up to 15 to 20 years behind South Africa in terms of digital development, they should not be held back in catch up by availability of IP resources don?t you think? Regards Ben From: Owen DeLong via RPD Sent: 15 October 2025 11:55 To: Noah Cc: RPD Subject: Re: [rpd] Questions about IP Allocation rate Do you really expect 17,000+ legitimate new entrants in the next X years (where X is the number of years you expect before catering to laggards is no longer a requirement) in the AFRINIC service area? I think that?s a pretty gross overestimate. Owen On Oct 15, 2025, at 00:39, Noah > wrote: ? On Wed, 15 Oct 2025, 9:42?am jordi.palet--- via RPD, > wrote: Is not for the peering (it is not needed even for IXPs, we can use IPv6-only), is for the NAT64. RFC6146 is widely supported by most vendors today and a bare minimum of /24 v4 space for translators is foresight grounded on reality of v4/v6 co-existance. More so for new entrants who must not be succummed to IPv$ brokers/leasers who stockpile to monetize in future based on scarcity. Noah Noah _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Wed Oct 15 11:40:57 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Wed, 15 Oct 2025 14:40:57 +0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking Message-ID: Hi Guys, So - Firstly a few notes on using the code I'm going to paste below. I created the BGP dump file on a juniper router by running a "show route protocol bgp | save bgp.dump.txt" and then copying that dump file to my local system from the Juniper router. Note - this produces a roughly 400meg file on a full table router and it takes quite a while to run the command. Then - I used the delegated-afrinic-extended-latest file downloaded from the stats ftp server. In the code below - if you wish to run similar - change the char BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match the pathing to the relevant files. Note that there is some weirdness in this code to deal with endianness - and I will openly admit its not the cleanest (or probably most efficient) code - but it does work and I've verified the results. I've pasted the code below the results section. So - first the results: Found 824064 total available addresses and 4482304 total reserved addresses 41.57.124.0/22 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 1024 addresses to potential hijack] 41.57.124.0/23 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 512 addresses to potential hijack] 41.57.124.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.57.125.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.57.126.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.57.127.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.77.64.0/21 fell between reserved range 41.77.64.0 -> 41.77.71.255 [Adding 2048 addresses to potential hijack] 41.138.192.0/24 fell between reserved range 41.138.192.0 -> 41.138.223.255 [Adding 256 addresses to potential hijack] 41.204.224.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.225.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.226.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.227.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.228.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.229.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.230.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.231.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.232.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.233.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.234.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.235.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.236.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.237.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.238.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.239.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.240.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.241.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.242.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.243.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.244.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.245.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.246.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.247.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.248.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.249.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.250.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.251.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.254.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.255.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.205.224.0/19 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 8192 addresses to potential hijack] 41.205.225.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.232.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.234.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.235.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.237.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.238.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.239.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.220.48.0/20 fell between reserved range 41.220.48.0 -> 41.220.63.255 [Adding 4096 addresses to potential hijack] 80.88.6.0/24 fell between reserved range 80.88.6.0 -> 80.88.6.255 [Adding 256 addresses to potential hijack] 102.128.74.0/24 fell between reserved range 102.128.72.0 -> 102.128.75.255 [Adding 256 addresses to potential hijack] 102.135.164.0/24 fell between reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential hijack] 102.135.165.0/24 fell between reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential hijack] 102.135.166.0/24 fell between reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential hijack] 102.219.128.0/24 fell between reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential hijack] 102.219.129.0/24 fell between reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential hijack] 102.219.130.0/24 fell between reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential hijack] 102.221.148.0/22 fell between reserved range 102.221.144.0 -> 102.221.151.255 [Adding 1024 addresses to potential hijack] 156.0.254.0/24 fell between reserved range 156.0.254.0 -> 156.0.254.255 [Adding 256 addresses to potential hijack] 160.119.208.0/24 fell between reserved range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to potential hijack] 160.119.209.0/24 fell between reserved range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to potential hijack] 164.160.192.0/21 fell between reserved range 164.160.192.0 -> 164.160.223.255 [Adding 2048 addresses to potential hijack] 169.255.164.0/22 fell between reserved range 169.255.164.0 -> 169.255.167.255 [Adding 1024 addresses to potential hijack] 193.188.7.0/24 fell between reserved range 193.188.7.0 -> 193.188.7.255 [Adding 256 addresses to potential hijack] 196.13.203.0/24 fell between reserved range 196.13.203.0 -> 196.13.203.255 [Adding 256 addresses to potential hijack] 196.20.60.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] 196.20.61.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] 196.20.62.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] 196.41.74.0/24 fell between reserved range 196.41.74.0 -> 196.41.74.255 [Adding 256 addresses to potential hijack] 196.43.252.0/24 fell between reserved range 196.43.252.0 -> 196.43.252.255 [Adding 256 addresses to potential hijack] 196.46.18.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to potential hijack] 196.46.19.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to potential hijack] 196.46.152.0/24 fell between reserved range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to potential hijack] 196.46.153.0/24 fell between reserved range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to potential hijack] 196.46.154.0/23 fell between reserved range 196.46.152.0 -> 196.46.159.255 [Adding 512 addresses to potential hijack] 196.50.21.0/24 fell between reserved range 196.50.21.0 -> 196.50.21.255 [Adding 256 addresses to potential hijack] 196.53.113.0/24 fell between reserved range 196.52.0.0 -> 196.55.255.255 [Adding 256 addresses to potential hijack] 196.54.72.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to potential hijack] 196.55.102.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to potential hijack] 196.63.243.0/24 fell between reserved range 196.62.0.0 -> 196.63.255.255 [Adding 256 addresses to potential hijack] 196.195.4.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] 196.195.15.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] 196.195.253.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] 197.157.200.0/22 fell between reserved range 197.157.200.0 -> 197.157.203.255 [Adding 1024 addresses to potential hijack] 197.231.248.0/22 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 1024 addresses to potential hijack] 197.231.248.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.231.249.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.231.250.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.231.251.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.234.208.0/24 fell between reserved range 197.234.208.0 -> 197.234.215.255 [Adding 256 addresses to potential hijack] 212.12.224.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.225.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.226.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.227.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.229.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.231.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.232.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.233.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.234.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.235.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.236.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.237.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.238.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.239.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.240.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.241.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.242.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.243.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.244.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.245.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.246.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.247.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.248.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.249.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.250.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.251.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.252.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.254.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.255.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] Found 50176 potentially hijacked addresses --- Below here is the code (I didn't know if I could send attachments to the RPD list so I just pasted the code straight) --- // // main.c // AfrinicAudit // // Created by Andrew Alston on 15/10/2025. // Code is considered open use with no restrictions. // #include #include #include #include char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; char AFRINIC_EXT[256] = "/Users/aalston/audit/delegated-afrinic-extended-latest"; struct routes { unsigned int network; unsigned int broadcast; unsigned int mask; unsigned short cidr; }; struct audit { struct routes *dfz; int dfz_count; struct routes *reserved; int total_resv; int rc; struct routes *available; int total_avail; int ac; }; int parse_afrinic_extended(char *afext, struct audit *output) { FILE *dump = fopen(afext, "r"); if(!dump) return -1; char buffer[1024] = {0}; char *delim; output->rc = 0; while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && strstr(buffer, "ipv4")) { output->rc++; } } output->reserved = calloc(output->rc, sizeof(struct routes)); if(!output->reserved) return -1; output->rc = 0; struct routes *resv = output->reserved; rewind(dump); while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && strstr(buffer, "ipv4")) { delim = strtok(buffer, "|"); for(int i = 0; i < 3; i++) delim = strtok(NULL, "|"); inet_pton(AF_INET, delim, &resv[output->rc].network); resv[output->rc].network = __builtin_bswap32(resv[output->rc].network); delim = strtok(NULL, "|"); unsigned int addr_count = atoi(delim); output->total_resv += addr_count; resv[output->rc].broadcast = resv[output->rc].network+(addr_count-1); resv[output->rc].network = __builtin_bswap32(resv[output->rc].network); resv[output->rc].broadcast = __builtin_bswap32(resv[output->rc].broadcast); resv[output->rc].mask = ~__builtin_bswap32((unsigned int)addr_count-1); output->rc++; } } rewind(dump); while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "available") && strstr(buffer, "ipv4")) { output->ac++; } } output->available = calloc(output->ac, sizeof(struct routes)); if(!output->available) return -1; struct routes *avail = output->available; rewind(dump); while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "available") && strstr(buffer, "ipv4")) { delim = strtok(buffer, "|"); for(int i = 0; i < 3; i++) delim = strtok(NULL, "|"); inet_pton(AF_INET, delim, &avail[output->ac].network); avail[output->ac].network = __builtin_bswap32(avail[output->ac].network); delim = strtok(NULL, "|"); unsigned int addr_count = atoi(delim); output->total_avail += addr_count; avail[output->ac].broadcast = avail[output->ac].network+(addr_count-1); avail[output->ac].mask = ~__builtin_bswap32((unsigned int)addr_count-1); output->ac++; } } fclose(dump); return 0; } int parse_dfz(char *dfz_dump, struct audit *output) { FILE *dump = fopen(dfz_dump, "r"); char buffer[1024] = {0}; int rc = 0, mult = 0, cidr = 0; char *delim; if(!dump) { return -1; } while(fgets(buffer, 1024, dump)) { if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") && strchr(buffer, '.')) { rc++; } } output->dfz = calloc(rc, sizeof(struct routes)); output->dfz_count = rc; if(!output->dfz) { return -1; } rewind(dump); rc = 0; while(fgets(buffer, 1024, dump)) { if(buffer[0] >= '1' && buffer[0] <= '9') { cidr = 0; delim = strtok(buffer, "/"); delim = strtok(NULL, "/"); if(!delim) { memset(buffer, 0, 1024); continue; } mult = 1; for(int i = 0; i < 3; i++) { if(delim[i] >= '0' && delim[i] <= '9') { cidr = cidr * mult+(9-('9'-delim[i])); mult*=10; } } delim = strchr(buffer, '.'); if(!delim) { memset(buffer, 0, 1024); continue; } output->dfz[rc].cidr = cidr; inet_pton(AF_INET, buffer, &output->dfz[rc].network); output->dfz[rc].cidr = cidr; output->dfz[rc].network = __builtin_bswap32((unsigned int)output->dfz[rc].network); output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); output->dfz[rc].broadcast = output->dfz[rc].network + ((~(unsigned int)0) >> cidr); output->dfz[rc].network = __builtin_bswap32((unsigned int)output->dfz[rc].network); output->dfz[rc].broadcast = __builtin_bswap32((unsigned int)output->dfz[rc].broadcast); rc++; memset(buffer, 0, 1024); } } fclose(dump); return 0; } int audit_reserved(struct audit *data) { int hijack_count = 0; for(int i = 0; i < data->dfz_count; i++) { unsigned int dfz_net = __builtin_bswap32((unsigned int)data->dfz[i].network); unsigned int dfz_bcast = __builtin_bswap32((unsigned int)data->dfz[i].broadcast); for(int r = 0; r < data->rc; r++) { unsigned int resv_net = __builtin_bswap32((unsigned int)data->reserved[r].network); unsigned int resv_bcast = __builtin_bswap32((unsigned int)data->reserved[r].broadcast); if(dfz_net >= resv_net && dfz_net <= resv_bcast) { hijack_count += ((dfz_bcast-dfz_net)+1); char dfz_route[INET_ADDRSTRLEN] = {0}; char resv_network[INET_ADDRSTRLEN] = {0}; char resv_broadcast[INET_ADDRSTRLEN] = {0}; inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, INET_ADDRSTRLEN); inet_ntop(AF_INET, &data->reserved[r].network, resv_network, INET_ADDRSTRLEN); inet_ntop(AF_INET, &data->reserved[r].broadcast, resv_broadcast, INET_ADDRSTRLEN); printf("%s/%d fell between reserved range %s -> %s [Adding %d addresses to potential hijack]\n", dfz_route, data->dfz[i].cidr, resv_network, resv_broadcast, (dfz_bcast-dfz_net)+1); } } for(int a = 0; a < data->ac; a++) { unsigned int avail_net = __builtin_bswap32((unsigned int)data->available[a].network); unsigned int avail_bcast = __builtin_bswap32((unsigned int)data->available[a].broadcast); if(dfz_net >= data->available[a].network && dfz_net <= data->available[a].broadcast) { hijack_count += ((data->available[a].broadcast-data->available[a].network)+1); char dfz_route[INET_ADDRSTRLEN] = {0}; char avail_network[INET_ADDRSTRLEN] = {0}; char avail_broadcast[INET_ADDRSTRLEN] = {0}; inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, INET_ADDRSTRLEN); inet_ntop(AF_INET, &avail_net, avail_network, INET_ADDRSTRLEN); inet_ntop(AF_INET, &avail_bcast, avail_broadcast, INET_ADDRSTRLEN); printf("%s/%d fell between available range %s -> %s\n", dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); } } } printf("Found %d potentially hijacked addresses\n", hijack_count); return 0; } int main(int argc, const char * argv[]) { struct audit data = {0}; if(parse_dfz(BGP_DUMP, &data)) return EXIT_FAILURE; if(parse_afrinic_extended(AFRINIC_EXT, &data)) return EXIT_FAILURE; printf("Found %d total available addresses and %d total reserved addresses\n", data.total_avail, data.total_resv); audit_reserved(&data); return EXIT_SUCCESS; } -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms-announce at afrinic.net Wed Oct 15 11:43:07 2025 From: comms-announce at afrinic.net (AFRINIC Announce) Date: Wed, 15 Oct 2025 11:43:07 +0000 Subject: [rpd] Register for the "Updating ICP-2: Advancing Internet Number Governance for the Future" Webinar on 21st October 2025 Message-ID: Dear Colleagues, You are invited to register for the webinar on "Updating ICP-2: Advancing Internet Number Governance for the Future" Webinar. * Date: Tuesday 21st October 2025 * Time: 10:00 -11:00 UTC * Duration: 1:00 Hr * Registration Link The Internet Coordination Policy 2 (ICP-2) was developed in 2001 through the Address Supporting Organization (ASO), with contributions from APNIC, ARIN, and RIPE NCC. Its purpose was to establish criteria for the recognition of new Regional Internet Registries (RIRs), serving as a framework to guide how RIRs are recognized and maintained. For more than two decades, ICP-2 has been the implicit standard for RIR accreditation and operations. However, the Internet ecosystem has evolved considerably since then ? both in scale and in governance complexity. Recognizing the need for modernization, the Number Resource Organization Executive Council (NRO EC), together with the Address Supporting Organization Address Council (ASO AC), launched an initiative to review and update ICP-2 to better reflect today?s realities. Among other discussions, the Council representatives will give a summary of the main changes between the two versions of the RIR Governance Documents and the rationale behind these changes. This summary of changes is also available on the NRO website As part of this review process, the Number Resource Organization Number Council (NRO NC) will host a webinar to share insights into the next phase of the ICP-2 update. The session will introduce the second draft of the ?Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries,? which is intended to replace the original ICP-2. Key Takeaways * Gain a clear understanding of the ongoing process to update ICP-2, a foundational policy that guides the recognition and operation of Regional Internet Registries (RIRs). * Understand the rationale behind the proposed updates and how they reflect today?s evolving Internet governance landscape. * Participate in the global consultation process. Secure your Spot Here Be sure to save the date and spread the word as your participation is key to making these sessions a success! ________________________________ Explore the full schedule and learn more about AFRINIC webinars on our Webinar Series Page. We look forward to having you join us for these insightful sessions! ________________________________ Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Wed Oct 15 11:54:50 2025 From: ben.roberts at afrinic.net (ben.roberts at afrinic.net) Date: Wed, 15 Oct 2025 14:54:50 +0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: References: Message-ID: <02e301dc3dca$83963660$8ac2a320$@afrinic.net> This is great Andrew. I feel like we should have more of this sort of thing and perhaps an IP address research hackathon will be a great idea. Your c is pretty good, I will give you a tip though. 2 useful features of c are to use // or /* */ to insert comments in the code e.g. // This is a comment Or /* This is a comment*/ The comments aren?t compiled in the code so you can write anything you like. Using comments like this is really helpful when sharing code with others, to help them understand it? ??? From: Andrew Alston Sent: 15 October 2025 14:41 To: RPD Subject: [rpd] Reserved Space/Available Space and potential hijacking Hi Guys, So - Firstly a few notes on using the code I'm going to paste below. I created the BGP dump file on a juniper router by running a "show route protocol bgp | save bgp.dump.txt" and then copying that dump file to my local system from the Juniper router. Note - this produces a roughly 400meg file on a full table router and it takes quite a while to run the command. Then - I used the delegated-afrinic-extended-latest file downloaded from the stats ftp server. In the code below - if you wish to run similar - change the char BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match the pathing to the relevant files. Note that there is some weirdness in this code to deal with endianness - and I will openly admit its not the cleanest (or probably most efficient) code - but it does work and I've verified the results. I've pasted the code below the results section. So - first the results: Found 824064 total available addresses and 4482304 total reserved addresses 41.57.124.0/22 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 1024 addresses to potential hijack] 41.57.124.0/23 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 512 addresses to potential hijack] 41.57.124.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.57.125.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.57.126.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.57.127.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] 41.77.64.0/21 fell between reserved range 41.77.64.0 -> 41.77.71.255 [Adding 2048 addresses to potential hijack] 41.138.192.0/24 fell between reserved range 41.138.192.0 -> 41.138.223.255 [Adding 256 addresses to potential hijack] 41.204.224.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.225.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.226.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.227.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.228.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.229.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.230.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.231.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.232.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.233.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.234.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.235.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.236.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.237.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.238.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.239.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.240.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.241.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.242.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.243.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.244.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.245.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.246.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.247.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.248.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.249.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.250.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.251.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.254.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.204.255.0/24 fell between reserved range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] 41.205.224.0/19 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 8192 addresses to potential hijack] 41.205.225.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.232.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.234.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.235.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.237.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.238.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.205.239.0/24 fell between reserved range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] 41.220.48.0/20 fell between reserved range 41.220.48.0 -> 41.220.63.255 [Adding 4096 addresses to potential hijack] 80.88.6.0/24 fell between reserved range 80.88.6.0 -> 80.88.6.255 [Adding 256 addresses to potential hijack] 102.128.74.0/24 fell between reserved range 102.128.72.0 -> 102.128.75.255 [Adding 256 addresses to potential hijack] 102.135.164.0/24 fell between reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential hijack] 102.135.165.0/24 fell between reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential hijack] 102.135.166.0/24 fell between reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential hijack] 102.219.128.0/24 fell between reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential hijack] 102.219.129.0/24 fell between reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential hijack] 102.219.130.0/24 fell between reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential hijack] 102.221.148.0/22 fell between reserved range 102.221.144.0 -> 102.221.151.255 [Adding 1024 addresses to potential hijack] 156.0.254.0/24 fell between reserved range 156.0.254.0 -> 156.0.254.255 [Adding 256 addresses to potential hijack] 160.119.208.0/24 fell between reserved range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to potential hijack] 160.119.209.0/24 fell between reserved range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to potential hijack] 164.160.192.0/21 fell between reserved range 164.160.192.0 -> 164.160.223.255 [Adding 2048 addresses to potential hijack] 169.255.164.0/22 fell between reserved range 169.255.164.0 -> 169.255.167.255 [Adding 1024 addresses to potential hijack] 193.188.7.0/24 fell between reserved range 193.188.7.0 -> 193.188.7.255 [Adding 256 addresses to potential hijack] 196.13.203.0/24 fell between reserved range 196.13.203.0 -> 196.13.203.255 [Adding 256 addresses to potential hijack] 196.20.60.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] 196.20.61.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] 196.20.62.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] 196.41.74.0/24 fell between reserved range 196.41.74.0 -> 196.41.74.255 [Adding 256 addresses to potential hijack] 196.43.252.0/24 fell between reserved range 196.43.252.0 -> 196.43.252.255 [Adding 256 addresses to potential hijack] 196.46.18.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to potential hijack] 196.46.19.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to potential hijack] 196.46.152.0/24 fell between reserved range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to potential hijack] 196.46.153.0/24 fell between reserved range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to potential hijack] 196.46.154.0/23 fell between reserved range 196.46.152.0 -> 196.46.159.255 [Adding 512 addresses to potential hijack] 196.50.21.0/24 fell between reserved range 196.50.21.0 -> 196.50.21.255 [Adding 256 addresses to potential hijack] 196.53.113.0/24 fell between reserved range 196.52.0.0 -> 196.55.255.255 [Adding 256 addresses to potential hijack] 196.54.72.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to potential hijack] 196.55.102.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to potential hijack] 196.63.243.0/24 fell between reserved range 196.62.0.0 -> 196.63.255.255 [Adding 256 addresses to potential hijack] 196.195.4.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] 196.195.15.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] 196.195.253.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] 197.157.200.0/22 fell between reserved range 197.157.200.0 -> 197.157.203.255 [Adding 1024 addresses to potential hijack] 197.231.248.0/22 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 1024 addresses to potential hijack] 197.231.248.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.231.249.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.231.250.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.231.251.0/24 fell between reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential hijack] 197.234.208.0/24 fell between reserved range 197.234.208.0 -> 197.234.215.255 [Adding 256 addresses to potential hijack] 212.12.224.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.225.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.226.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.227.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.229.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.231.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.232.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.233.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.234.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.235.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.236.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.237.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.238.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.239.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.240.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.241.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.242.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.243.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.244.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.245.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.246.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.247.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.248.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.249.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.250.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.251.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.252.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.254.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] 212.12.255.0/24 fell between reserved range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] Found 50176 potentially hijacked addresses --- Below here is the code (I didn't know if I could send attachments to the RPD list so I just pasted the code straight) --- // // main.c // AfrinicAudit // // Created by Andrew Alston on 15/10/2025. // Code is considered open use with no restrictions. // #include #include #include #include char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; char AFRINIC_EXT[256] = "/Users/aalston/audit/delegated-afrinic-extended-latest"; struct routes { unsigned int network; unsigned int broadcast; unsigned int mask; unsigned short cidr; }; struct audit { struct routes *dfz; int dfz_count; struct routes *reserved; int total_resv; int rc; struct routes *available; int total_avail; int ac; }; int parse_afrinic_extended(char *afext, struct audit *output) { FILE *dump = fopen(afext, "r"); if(!dump) return -1; char buffer[1024] = {0}; char *delim; output->rc = 0; while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && strstr(buffer, "ipv4")) { output->rc++; } } output->reserved = calloc(output->rc, sizeof(struct routes)); if(!output->reserved) return -1; output->rc = 0; struct routes *resv = output->reserved; rewind(dump); while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && strstr(buffer, "ipv4")) { delim = strtok(buffer, "|"); for(int i = 0; i < 3; i++) delim = strtok(NULL, "|"); inet_pton(AF_INET, delim, &resv[output->rc].network); resv[output->rc].network = __builtin_bswap32(resv[output->rc].network); delim = strtok(NULL, "|"); unsigned int addr_count = atoi(delim); output->total_resv += addr_count; resv[output->rc].broadcast = resv[output->rc].network+(addr_count-1); resv[output->rc].network = __builtin_bswap32(resv[output->rc].network); resv[output->rc].broadcast = __builtin_bswap32(resv[output->rc].broadcast); resv[output->rc].mask = ~__builtin_bswap32((unsigned int)addr_count-1); output->rc++; } } rewind(dump); while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "available") && strstr(buffer, "ipv4")) { output->ac++; } } output->available = calloc(output->ac, sizeof(struct routes)); if(!output->available) return -1; struct routes *avail = output->available; rewind(dump); while(fgets(buffer, 1024, dump)) { if(strstr(buffer, "ZZ") && strstr(buffer, "available") && strstr(buffer, "ipv4")) { delim = strtok(buffer, "|"); for(int i = 0; i < 3; i++) delim = strtok(NULL, "|"); inet_pton(AF_INET, delim, &avail[output->ac].network); avail[output->ac].network = __builtin_bswap32(avail[output->ac].network); delim = strtok(NULL, "|"); unsigned int addr_count = atoi(delim); output->total_avail += addr_count; avail[output->ac].broadcast = avail[output->ac].network+(addr_count-1); avail[output->ac].mask = ~__builtin_bswap32((unsigned int)addr_count-1); output->ac++; } } fclose(dump); return 0; } int parse_dfz(char *dfz_dump, struct audit *output) { FILE *dump = fopen(dfz_dump, "r"); char buffer[1024] = {0}; int rc = 0, mult = 0, cidr = 0; char *delim; if(!dump) { return -1; } while(fgets(buffer, 1024, dump)) { if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") && strchr(buffer, '.')) { rc++; } } output->dfz = calloc(rc, sizeof(struct routes)); output->dfz_count = rc; if(!output->dfz) { return -1; } rewind(dump); rc = 0; while(fgets(buffer, 1024, dump)) { if(buffer[0] >= '1' && buffer[0] <= '9') { cidr = 0; delim = strtok(buffer, "/"); delim = strtok(NULL, "/"); if(!delim) { memset(buffer, 0, 1024); continue; } mult = 1; for(int i = 0; i < 3; i++) { if(delim[i] >= '0' && delim[i] <= '9') { cidr = cidr * mult+(9-('9'-delim[i])); mult*=10; } } delim = strchr(buffer, '.'); if(!delim) { memset(buffer, 0, 1024); continue; } output->dfz[rc].cidr = cidr; inet_pton(AF_INET, buffer, &output->dfz[rc].network); output->dfz[rc].cidr = cidr; output->dfz[rc].network = __builtin_bswap32((unsigned int)output->dfz[rc].network); output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); output->dfz[rc].broadcast = output->dfz[rc].network + ((~(unsigned int)0) >> cidr); output->dfz[rc].network = __builtin_bswap32((unsigned int)output->dfz[rc].network); output->dfz[rc].broadcast = __builtin_bswap32((unsigned int)output->dfz[rc].broadcast); rc++; memset(buffer, 0, 1024); } } fclose(dump); return 0; } int audit_reserved(struct audit *data) { int hijack_count = 0; for(int i = 0; i < data->dfz_count; i++) { unsigned int dfz_net = __builtin_bswap32((unsigned int)data->dfz[i].network); unsigned int dfz_bcast = __builtin_bswap32((unsigned int)data->dfz[i].broadcast); for(int r = 0; r < data->rc; r++) { unsigned int resv_net = __builtin_bswap32((unsigned int)data->reserved[r].network); unsigned int resv_bcast = __builtin_bswap32((unsigned int)data->reserved[r].broadcast); if(dfz_net >= resv_net && dfz_net <= resv_bcast) { hijack_count += ((dfz_bcast-dfz_net)+1); char dfz_route[INET_ADDRSTRLEN] = {0}; char resv_network[INET_ADDRSTRLEN] = {0}; char resv_broadcast[INET_ADDRSTRLEN] = {0}; inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, INET_ADDRSTRLEN); inet_ntop(AF_INET, &data->reserved[r].network, resv_network, INET_ADDRSTRLEN); inet_ntop(AF_INET, &data->reserved[r].broadcast, resv_broadcast, INET_ADDRSTRLEN); printf("%s/%d fell between reserved range %s -> %s [Adding %d addresses to potential hijack]\n", dfz_route, data->dfz[i].cidr, resv_network, resv_broadcast, (dfz_bcast-dfz_net)+1); } } for(int a = 0; a < data->ac; a++) { unsigned int avail_net = __builtin_bswap32((unsigned int)data->available[a].network); unsigned int avail_bcast = __builtin_bswap32((unsigned int)data->available[a].broadcast); if(dfz_net >= data->available[a].network && dfz_net <= data->available[a].broadcast) { hijack_count += ((data->available[a].broadcast-data->available[a].network)+1); char dfz_route[INET_ADDRSTRLEN] = {0}; char avail_network[INET_ADDRSTRLEN] = {0}; char avail_broadcast[INET_ADDRSTRLEN] = {0}; inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, INET_ADDRSTRLEN); inet_ntop(AF_INET, &avail_net, avail_network, INET_ADDRSTRLEN); inet_ntop(AF_INET, &avail_bcast, avail_broadcast, INET_ADDRSTRLEN); printf("%s/%d fell between available range %s -> %s\n", dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); } } } printf("Found %d potentially hijacked addresses\n", hijack_count); return 0; } int main(int argc, const char * argv[]) { struct audit data = {0}; if(parse_dfz(BGP_DUMP, &data)) return EXIT_FAILURE; if(parse_afrinic_extended(AFRINIC_EXT, &data)) return EXIT_FAILURE; printf("Found %d total available addresses and %d total reserved addresses\n", data.total_avail, data.total_resv); audit_reserved(&data); return EXIT_SUCCESS; } -------------- next part -------------- An HTML attachment was scrubbed... URL: From fhfrediani at gmail.com Wed Oct 15 12:14:00 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Wed, 15 Oct 2025 09:14:00 -0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: References: Message-ID: Would it be possible to get detailed information about AfriNic prefixes that are currently being announced by different ASNs they are linked to and potentially being used out of the Africa region as well ? That would be a pretty interesting information to see. Regards Fernando On 10/15/2025 8:40 AM, Andrew Alston wrote: > Hi Guys, > > So - Firstly a few notes on using the code I'm going to paste below. > > I created the BGP dump file on a juniper router by running a "show > route protocol bgp | save bgp.dump.txt" and then copying that dump > file to my local system from the Juniper router.? Note - this produces > a roughly 400meg file on a full table router and it takes quite a > while to run the command. > Then - I used the delegated-afrinic-extended-latest file downloaded > from the stats ftp server. > > In the code below - if you wish to run similar - change the char > BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match the > pathing to the relevant files. > > Note that there is some weirdness?in this code to deal with endianness > - and I will openly admit its not the cleanest (or probably most > efficient) code - but it does work and I've verified the results. > > I've pasted the code below the results section. > > So - first the results: > > Found 824064 total available addresses and 4482304 total reserved > addresses > 41.57.124.0/22 fell between reserved range > 41.57.124.0 -> 41.57.127.255 [Adding 1024 addresses to potential hijack] > 41.57.124.0/23 fell between reserved range > 41.57.124.0 -> 41.57.127.255 [Adding 512 addresses to potential hijack] > 41.57.124.0/24 fell between reserved range > 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] > 41.57.125.0/24 fell between reserved range > 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] > 41.57.126.0/24 fell between reserved range > 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] > 41.57.127.0/24 fell between reserved range > 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to potential hijack] > 41.77.64.0/21 fell between reserved range > 41.77.64.0 -> 41.77.71.255 [Adding 2048 addresses to potential hijack] > 41.138.192.0/24 fell between reserved range > 41.138.192.0 -> 41.138.223.255 [Adding 256 addresses to potential hijack] > 41.204.224.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.225.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.226.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.227.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.228.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.229.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.230.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.231.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.232.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.233.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.234.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.235.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.236.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.237.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.238.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.239.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.240.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.241.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.242.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.243.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.244.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.245.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.246.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.247.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.248.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.249.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.250.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.251.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.254.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.255.0/24 fell between reserved range > 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.205.224.0/19 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 8192 addresses to potential hijack] > 41.205.225.0/24 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.232.0/24 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.234.0/24 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.235.0/24 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.237.0/24 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.238.0/24 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.239.0/24 fell between reserved range > 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.220.48.0/20 fell between reserved range > 41.220.48.0 -> 41.220.63.255 [Adding 4096 addresses to potential hijack] > 80.88.6.0/24 fell between reserved range > 80.88.6.0 -> 80.88.6.255 [Adding 256 addresses to potential hijack] > 102.128.74.0/24 fell between reserved range > 102.128.72.0 -> 102.128.75.255 [Adding 256 addresses to potential hijack] > 102.135.164.0/24 fell between reserved range > 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential > hijack] > 102.135.165.0/24 fell between reserved range > 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential > hijack] > 102.135.166.0/24 fell between reserved range > 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to potential > hijack] > 102.219.128.0/24 fell between reserved range > 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential > hijack] > 102.219.129.0/24 fell between reserved range > 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential > hijack] > 102.219.130.0/24 fell between reserved range > 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to potential > hijack] > 102.221.148.0/22 fell between reserved range > 102.221.144.0 -> 102.221.151.255 [Adding 1024 addresses to potential > hijack] > 156.0.254.0/24 fell between reserved range > 156.0.254.0 -> 156.0.254.255 [Adding 256 addresses to potential hijack] > 160.119.208.0/24 fell between reserved range > 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to potential > hijack] > 160.119.209.0/24 fell between reserved range > 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to potential > hijack] > 164.160.192.0/21 fell between reserved range > 164.160.192.0 -> 164.160.223.255 [Adding 2048 addresses to potential > hijack] > 169.255.164.0/22 fell between reserved range > 169.255.164.0 -> 169.255.167.255 [Adding 1024 addresses to potential > hijack] > 193.188.7.0/24 fell between reserved range > 193.188.7.0 -> 193.188.7.255 [Adding 256 addresses to potential hijack] > 196.13.203.0/24 fell between reserved range > 196.13.203.0 -> 196.13.203.255 [Adding 256 addresses to potential hijack] > 196.20.60.0/24 fell between reserved range > 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] > 196.20.61.0/24 fell between reserved range > 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] > 196.20.62.0/24 fell between reserved range > 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to potential hijack] > 196.41.74.0/24 fell between reserved range > 196.41.74.0 -> 196.41.74.255 [Adding 256 addresses to potential hijack] > 196.43.252.0/24 fell between reserved range > 196.43.252.0 -> 196.43.252.255 [Adding 256 addresses to potential hijack] > 196.46.18.0/24 fell between reserved range > 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to potential hijack] > 196.46.19.0/24 fell between reserved range > 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to potential hijack] > 196.46.152.0/24 fell between reserved range > 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.153.0/24 fell between reserved range > 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.154.0/23 fell between reserved range > 196.46.152.0 -> 196.46.159.255 [Adding 512 addresses to potential hijack] > 196.50.21.0/24 fell between reserved range > 196.50.21.0 -> 196.50.21.255 [Adding 256 addresses to potential hijack] > 196.53.113.0/24 fell between reserved range > 196.52.0.0 -> 196.55.255.255 [Adding 256 addresses to potential hijack] > 196.54.72.0/23 fell between reserved range > 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to potential hijack] > 196.55.102.0/23 fell between reserved range > 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to potential hijack] > 196.63.243.0/24 fell between reserved range > 196.62.0.0 -> 196.63.255.255 [Adding 256 addresses to potential hijack] > 196.195.4.0/24 fell between reserved range > 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] > 196.195.15.0/24 fell between reserved range > 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] > 196.195.253.0/24 fell between reserved range > 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to potential hijack] > 197.157.200.0/22 fell between reserved range > 197.157.200.0 -> 197.157.203.255 [Adding 1024 addresses to potential > hijack] > 197.231.248.0/22 fell between reserved range > 197.231.248.0 -> 197.231.251.255 [Adding 1024 addresses to potential > hijack] > 197.231.248.0/24 fell between reserved range > 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential > hijack] > 197.231.249.0/24 fell between reserved range > 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential > hijack] > 197.231.250.0/24 fell between reserved range > 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential > hijack] > 197.231.251.0/24 fell between reserved range > 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to potential > hijack] > 197.234.208.0/24 fell between reserved range > 197.234.208.0 -> 197.234.215.255 [Adding 256 addresses to potential > hijack] > 212.12.224.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.225.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.226.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.227.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.229.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.231.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.232.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.233.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.234.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.235.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.236.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.237.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.238.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.239.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.240.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.241.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.242.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.243.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.244.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.245.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.246.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.247.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.248.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.249.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.250.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.251.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.252.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.254.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.255.0/24 fell between reserved range > 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to potential hijack] > Found 50176 potentially hijacked addresses > > --- Below here is the code (I didn't know if I could send attachments > to the RPD list so I just pasted the code straight) --- > > // > // ?main.c > // ?AfrinicAudit > // > // ?Created by Andrew Alston on 15/10/2025. > // ?Code is considered open use with no restrictions. > // > > #include > #include > #include > #include > > char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; > char AFRINIC_EXT[256] = > "/Users/aalston/audit/delegated-afrinic-extended-latest"; > > struct routes { > ? ? unsigned int network; > ? ? unsigned int broadcast; > ? ? unsigned int mask; > ? ? unsigned short cidr; > }; > > struct audit { > ? ? struct routes *dfz; > ? ? int dfz_count; > ? ? struct routes *reserved; > ? ? int total_resv; > ? ? int rc; > ? ? struct routes *available; > ? ? int total_avail; > ? ? int ac; > }; > > int parse_afrinic_extended(char *afext, struct audit *output) { > ? ? FILE *dump = fopen(afext, "r"); > ? ? if(!dump) > ? ? ? ? return -1; > ? ? char buffer[1024] = {0}; > ? ? char *delim; > ? ? output->rc = 0; > ? ? while(fgets(buffer, 1024, dump)) { > ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > ? ? ? ? ? ? output->rc++; > ? ? ? ? } > ? ? } > ? ? output->reserved = calloc(output->rc, sizeof(struct routes)); > ? ? if(!output->reserved) > ? ? ? ? return -1; > ? ? output->rc = 0; > ? ? struct routes *resv = output->reserved; > ? ? rewind(dump); > ? ? while(fgets(buffer, 1024, dump)) { > ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > ? ? ? ? ? ? delim = strtok(buffer, "|"); > ? ? ? ? ? ? for(int i = 0; i < 3; i++) > ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); > ? ? ? ? ? ? inet_pton(AF_INET, delim, &resv[output->rc].network); > ? ? ? ? ? ? resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > ? ? ? ? ? ? delim = strtok(NULL, "|"); > ? ? ? ? ? ? unsigned int addr_count = atoi(delim); > ? ? ? ? ? ? output->total_resv += addr_count; > ? ? ? ? ? ? resv[output->rc].broadcast = > resv[output->rc].network+(addr_count-1); > ? ? ? ? ? ? resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > ? ? ? ? ? ? resv[output->rc].broadcast = > __builtin_bswap32(resv[output->rc].broadcast); > ? ? ? ? ? ? resv[output->rc].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > ? ? ? ? ? ? output->rc++; > ? ? ? ? } > ? ? } > ? ? rewind(dump); > ? ? while(fgets(buffer, 1024, dump)) { > ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > ? ? ? ? ? ? output->ac++; > ? ? ? ? } > ? ? } > ? ? output->available = calloc(output->ac, sizeof(struct routes)); > ? ? if(!output->available) > ? ? ? ? return -1; > ? ? struct routes *avail = output->available; > ? ? rewind(dump); > ? ? while(fgets(buffer, 1024, dump)) { > ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > ? ? ? ? ? ? delim = strtok(buffer, "|"); > ? ? ? ? ? ? for(int i = 0; i < 3; i++) > ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); > ? ? ? ? ? ? inet_pton(AF_INET, delim, &avail[output->ac].network); > ? ? ? ? ? ? avail[output->ac].network = > __builtin_bswap32(avail[output->ac].network); > ? ? ? ? ? ? delim = strtok(NULL, "|"); > ? ? ? ? ? ? unsigned int addr_count = atoi(delim); > ? ? ? ? ? ? output->total_avail += addr_count; > ? ? ? ? ? ? avail[output->ac].broadcast = > avail[output->ac].network+(addr_count-1); > ? ? ? ? ? ? avail[output->ac].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > ? ? ? ? ? ? output->ac++; > ? ? ? ? } > ? ? } > ? ? fclose(dump); > ? ? return 0; > } > > int parse_dfz(char *dfz_dump, struct audit *output) { > ? ? FILE *dump = fopen(dfz_dump, "r"); > ? ? char buffer[1024] = {0}; > ? ? int rc = 0, mult = 0, cidr = 0; > ? ? char *delim; > ? ? if(!dump) { > ? ? ? ? return -1; > ? ? } > ? ? while(fgets(buffer, 1024, dump)) { > ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") > && strchr(buffer, '.')) { > ? ? ? ? ? ? rc++; > ? ? ? ? } > ? ? } > ? ? output->dfz = calloc(rc, sizeof(struct routes)); > ? ? output->dfz_count = rc; > ? ? if(!output->dfz) { > ? ? ? ? return -1; > ? ? } > ? ? rewind(dump); > ? ? rc = 0; > ? ? while(fgets(buffer, 1024, dump)) { > ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9') { > ? ? ? ? ? ? cidr = 0; > ? ? ? ? ? ? delim = strtok(buffer, "/"); > ? ? ? ? ? ? delim = strtok(NULL, "/"); > ? ? ? ? ? ? if(!delim) { > ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); > ? ? ? ? ? ? ? ? continue; > ? ? ? ? ? ? } > ? ? ? ? ? ? mult = 1; > ? ? ? ? ? ? for(int i = 0; i < 3; i++) { > ? ? ? ? ? ? ? ? if(delim[i] >= '0' && delim[i] <= '9') { > ? ? ? ? ? ? ? ? ? ? cidr = cidr * mult+(9-('9'-delim[i])); > ? ? ? ? ? ? ? ? ? ? mult*=10; > ? ? ? ? ? ? ? ? } > ? ? ? ? ? ? } > ? ? ? ? ? ? delim = strchr(buffer, '.'); > ? ? ? ? ? ? if(!delim) { > ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); > ? ? ? ? ? ? ? ? continue; > ? ? ? ? ? ? } > ? ? ? ? ? ? output->dfz[rc].cidr = cidr; > ? ? ? ? ? ? inet_pton(AF_INET, buffer, &output->dfz[rc].network); > ? ? ? ? ? ? output->dfz[rc].cidr = cidr; > ? ? ? ? ? ? output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > ? ? ? ? ? ? output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); > ? ? ? ? ? ? output->dfz[rc].broadcast = output->dfz[rc].network + > ((~(unsigned int)0) >> cidr); > ? ? ? ? ? ? output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > ? ? ? ? ? ? output->dfz[rc].broadcast = __builtin_bswap32((unsigned > int)output->dfz[rc].broadcast); > ? ? ? ? ? ? rc++; > ? ? ? ? ? ? memset(buffer, 0, 1024); > ? ? ? ? } > ? ? } > ? ? fclose(dump); > ? ? return 0; > } > > int audit_reserved(struct audit *data) { > ? ? int hijack_count = 0; > ? ? for(int i = 0; i < data->dfz_count; i++) { > ? ? ? ? unsigned int dfz_net = __builtin_bswap32((unsigned > int)data->dfz[i].network); > ? ? ? ? unsigned int dfz_bcast = __builtin_bswap32((unsigned > int)data->dfz[i].broadcast); > ? ? ? ? for(int r = 0; r < data->rc; r++) { > ? ? ? ? ? ? unsigned int resv_net = __builtin_bswap32((unsigned > int)data->reserved[r].network); > ? ? ? ? ? ? unsigned int resv_bcast = __builtin_bswap32((unsigned > int)data->reserved[r].broadcast); > ? ? ? ? ? ? if(dfz_net >= resv_net && dfz_net <= resv_bcast) { > ? ? ? ? ? ? ? ? hijack_count += ((dfz_bcast-dfz_net)+1); > ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; > ? ? ? ? ? ? ? ? char resv_network[INET_ADDRSTRLEN] = {0}; > ? ? ? ? ? ? ? ? char resv_broadcast[INET_ADDRSTRLEN] = {0}; > ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->reserved[r].network, > resv_network, INET_ADDRSTRLEN); > ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->reserved[r].broadcast, > resv_broadcast, INET_ADDRSTRLEN); > ? ? ? ? ? ? ? ? printf("%s/%d fell between reserved range %s -> %s > [Adding %d addresses to potential hijack]\n", > ? ? ? ? ? ? ? ? ? ? ? ?dfz_route, data->dfz[i].cidr, resv_network, > resv_broadcast, (dfz_bcast-dfz_net)+1); > ? ? ? ? ? ? } > ? ? ? ? } > ? ? ? ? for(int a = 0; a < data->ac; a++) { > ? ? ? ? ? ? unsigned int avail_net = __builtin_bswap32((unsigned > int)data->available[a].network); > ? ? ? ? ? ? unsigned int avail_bcast = __builtin_bswap32((unsigned > int)data->available[a].broadcast); > ? ? ? ? ? ? if(dfz_net >= data->available[a].network && dfz_net <= > data->available[a].broadcast) { > ? ? ? ? ? ? ? ? hijack_count += > ((data->available[a].broadcast-data->available[a].network)+1); > ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; > ? ? ? ? ? ? ? ? char avail_network[INET_ADDRSTRLEN] = {0}; > ? ? ? ? ? ? ? ? char avail_broadcast[INET_ADDRSTRLEN] = {0}; > ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_net, avail_network, > INET_ADDRSTRLEN); > ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_bcast, avail_broadcast, > INET_ADDRSTRLEN); > ? ? ? ? ? ? ? ? printf("%s/%d fell between available range %s -> > %s\n", dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); > ? ? ? ? ? ? } > ? ? ? ? } > ? ? } > ? ? printf("Found %d potentially hijacked addresses\n", hijack_count); > ? ? return 0; > } > > int main(int argc, const char * argv[]) { > ? ? struct audit data = {0}; > ? ? if(parse_dfz(BGP_DUMP, &data)) > ? ? ? ? return EXIT_FAILURE; > ? ? if(parse_afrinic_extended(AFRINIC_EXT, &data)) > ? ? ? ? return EXIT_FAILURE; > ? ? printf("Found %d total available addresses and %d total reserved > addresses\n", data.total_avail, data.total_resv); > ? ? audit_reserved(&data); > ? ? return EXIT_SUCCESS; > } > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Wed Oct 15 12:17:03 2025 From: noah at neo.co.tz (Noah) Date: Wed, 15 Oct 2025 15:17:03 +0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: <02e301dc3dca$83963660$8ac2a320$@afrinic.net> References: <02e301dc3dca$83963660$8ac2a320$@afrinic.net> Message-ID: Hi Andrew In addition to Ben's comment, please share the link to the github/repo of the code assuming it's public. Cheers, *.**/noah* On Wed, Oct 15, 2025 at 3:06?PM ben.roberts--- via RPD wrote: > This is great Andrew. I feel like we should have more of this sort of > thing and perhaps an IP address research hackathon will be a great idea. > > > > Your c is pretty good, I will give you a tip though. > > > > 2 useful features of c are to use // or /* */ to insert comments in the > code > > e.g. > > // This is a comment > > Or > > /* This is a comment*/ > > > > The comments aren?t compiled in the code so you can write anything you > like. Using comments like this is really helpful when sharing code with > others, to help them understand it? > > > > > > ??? > > > > *From:* Andrew Alston > *Sent:* 15 October 2025 14:41 > *To:* RPD > *Subject:* [rpd] Reserved Space/Available Space and potential hijacking > > > > Hi Guys, > > > > So - Firstly a few notes on using the code I'm going to paste below. > > > > I created the BGP dump file on a juniper router by running a "show route > protocol bgp | save bgp.dump.txt" and then copying that dump file to my > local system from the Juniper router. Note - this produces a roughly > 400meg file on a full table router and it takes quite a while to run the > command. > > Then - I used the delegated-afrinic-extended-latest file downloaded from > the stats ftp server. > > > > In the code below - if you wish to run similar - change the char > BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match the > pathing to the relevant files. > > > > Note that there is some weirdness in this code to deal with endianness - > and I will openly admit its not the cleanest (or probably most efficient) > code - but it does work and I've verified the results. > > > > I've pasted the code below the results section. > > > > So - first the results: > > > > Found 824064 total available addresses and 4482304 total reserved addresses > 41.57.124.0/22 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 1024 addresses to potential hijack] > 41.57.124.0/23 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 512 addresses to potential hijack] > 41.57.124.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.125.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.126.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.127.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.77.64.0/21 fell between reserved range 41.77.64.0 -> 41.77.71.255 > [Adding 2048 addresses to potential hijack] > 41.138.192.0/24 fell between reserved range 41.138.192.0 -> > 41.138.223.255 [Adding 256 addresses to potential hijack] > 41.204.224.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.225.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.226.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.227.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.228.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.229.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.230.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.231.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.232.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.233.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.234.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.235.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.236.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.237.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.238.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.239.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.240.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.241.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.242.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.243.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.244.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.245.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.246.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.247.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.248.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.249.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.250.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.251.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.254.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.255.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.205.224.0/19 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 8192 addresses to potential hijack] > 41.205.225.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.232.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.234.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.235.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.237.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.238.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.239.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.220.48.0/20 fell between reserved range 41.220.48.0 -> 41.220.63.255 > [Adding 4096 addresses to potential hijack] > 80.88.6.0/24 fell between reserved range 80.88.6.0 -> 80.88.6.255 [Adding > 256 addresses to potential hijack] > 102.128.74.0/24 fell between reserved range 102.128.72.0 -> > 102.128.75.255 [Adding 256 addresses to potential hijack] > 102.135.164.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.135.165.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.135.166.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.219.128.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.219.129.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.219.130.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.221.148.0/22 fell between reserved range 102.221.144.0 -> > 102.221.151.255 [Adding 1024 addresses to potential hijack] > 156.0.254.0/24 fell between reserved range 156.0.254.0 -> 156.0.254.255 > [Adding 256 addresses to potential hijack] > 160.119.208.0/24 fell between reserved range 160.119.208.0 -> > 160.119.211.255 [Adding 256 addresses to potential hijack] > 160.119.209.0/24 fell between reserved range 160.119.208.0 -> > 160.119.211.255 [Adding 256 addresses to potential hijack] > 164.160.192.0/21 fell between reserved range 164.160.192.0 -> > 164.160.223.255 [Adding 2048 addresses to potential hijack] > 169.255.164.0/22 fell between reserved range 169.255.164.0 -> > 169.255.167.255 [Adding 1024 addresses to potential hijack] > 193.188.7.0/24 fell between reserved range 193.188.7.0 -> 193.188.7.255 > [Adding 256 addresses to potential hijack] > 196.13.203.0/24 fell between reserved range 196.13.203.0 -> > 196.13.203.255 [Adding 256 addresses to potential hijack] > 196.20.60.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.20.61.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.20.62.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.41.74.0/24 fell between reserved range 196.41.74.0 -> 196.41.74.255 > [Adding 256 addresses to potential hijack] > 196.43.252.0/24 fell between reserved range 196.43.252.0 -> > 196.43.252.255 [Adding 256 addresses to potential hijack] > 196.46.18.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 > [Adding 256 addresses to potential hijack] > 196.46.19.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 > [Adding 256 addresses to potential hijack] > 196.46.152.0/24 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.153.0/24 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.154.0/23 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 512 addresses to potential hijack] > 196.50.21.0/24 fell between reserved range 196.50.21.0 -> 196.50.21.255 > [Adding 256 addresses to potential hijack] > 196.53.113.0/24 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 256 addresses to potential hijack] > 196.54.72.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 512 addresses to potential hijack] > 196.55.102.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 512 addresses to potential hijack] > 196.63.243.0/24 fell between reserved range 196.62.0.0 -> 196.63.255.255 > [Adding 256 addresses to potential hijack] > 196.195.4.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 > [Adding 256 addresses to potential hijack] > 196.195.15.0/24 fell between reserved range 196.194.0.0 -> > 196.195.255.255 [Adding 256 addresses to potential hijack] > 196.195.253.0/24 fell between reserved range 196.194.0.0 -> > 196.195.255.255 [Adding 256 addresses to potential hijack] > 197.157.200.0/22 fell between reserved range 197.157.200.0 -> > 197.157.203.255 [Adding 1024 addresses to potential hijack] > 197.231.248.0/22 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 1024 addresses to potential hijack] > 197.231.248.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.249.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.250.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.251.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.234.208.0/24 fell between reserved range 197.234.208.0 -> > 197.234.215.255 [Adding 256 addresses to potential hijack] > 212.12.224.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.225.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.226.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.227.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.229.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.231.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.232.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.233.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.234.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.235.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.236.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.237.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.238.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.239.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.240.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.241.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.242.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.243.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.244.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.245.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.246.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.247.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.248.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.249.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.250.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.251.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.252.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.254.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.255.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > Found 50176 potentially hijacked addresses > > > > --- Below here is the code (I didn't know if I could send attachments to > the RPD list so I just pasted the code straight) --- > > > > // > // main.c > // AfrinicAudit > // > // Created by Andrew Alston on 15/10/2025. > // Code is considered open use with no restrictions. > // > > #include > #include > #include > #include > > char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; > char AFRINIC_EXT[256] = > "/Users/aalston/audit/delegated-afrinic-extended-latest"; > > struct routes { > unsigned int network; > unsigned int broadcast; > unsigned int mask; > unsigned short cidr; > }; > > struct audit { > struct routes *dfz; > int dfz_count; > struct routes *reserved; > int total_resv; > int rc; > struct routes *available; > int total_avail; > int ac; > }; > > int parse_afrinic_extended(char *afext, struct audit *output) { > FILE *dump = fopen(afext, "r"); > if(!dump) > return -1; > char buffer[1024] = {0}; > char *delim; > output->rc = 0; > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > output->rc++; > } > } > output->reserved = calloc(output->rc, sizeof(struct routes)); > if(!output->reserved) > return -1; > output->rc = 0; > struct routes *resv = output->reserved; > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > delim = strtok(buffer, "|"); > for(int i = 0; i < 3; i++) > delim = strtok(NULL, "|"); > inet_pton(AF_INET, delim, &resv[output->rc].network); > resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > delim = strtok(NULL, "|"); > unsigned int addr_count = atoi(delim); > output->total_resv += addr_count; > resv[output->rc].broadcast = > resv[output->rc].network+(addr_count-1); > resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > resv[output->rc].broadcast = > __builtin_bswap32(resv[output->rc].broadcast); > resv[output->rc].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > output->rc++; > } > } > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > output->ac++; > } > } > output->available = calloc(output->ac, sizeof(struct routes)); > if(!output->available) > return -1; > struct routes *avail = output->available; > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > delim = strtok(buffer, "|"); > for(int i = 0; i < 3; i++) > delim = strtok(NULL, "|"); > inet_pton(AF_INET, delim, &avail[output->ac].network); > avail[output->ac].network = > __builtin_bswap32(avail[output->ac].network); > delim = strtok(NULL, "|"); > unsigned int addr_count = atoi(delim); > output->total_avail += addr_count; > avail[output->ac].broadcast = > avail[output->ac].network+(addr_count-1); > avail[output->ac].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > output->ac++; > } > } > fclose(dump); > return 0; > } > > int parse_dfz(char *dfz_dump, struct audit *output) { > FILE *dump = fopen(dfz_dump, "r"); > char buffer[1024] = {0}; > int rc = 0, mult = 0, cidr = 0; > char *delim; > if(!dump) { > return -1; > } > while(fgets(buffer, 1024, dump)) { > if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") && > strchr(buffer, '.')) { > rc++; > } > } > output->dfz = calloc(rc, sizeof(struct routes)); > output->dfz_count = rc; > if(!output->dfz) { > return -1; > } > rewind(dump); > rc = 0; > while(fgets(buffer, 1024, dump)) { > if(buffer[0] >= '1' && buffer[0] <= '9') { > cidr = 0; > delim = strtok(buffer, "/"); > delim = strtok(NULL, "/"); > if(!delim) { > memset(buffer, 0, 1024); > continue; > } > mult = 1; > for(int i = 0; i < 3; i++) { > if(delim[i] >= '0' && delim[i] <= '9') { > cidr = cidr * mult+(9-('9'-delim[i])); > mult*=10; > } > } > delim = strchr(buffer, '.'); > if(!delim) { > memset(buffer, 0, 1024); > continue; > } > output->dfz[rc].cidr = cidr; > inet_pton(AF_INET, buffer, &output->dfz[rc].network); > output->dfz[rc].cidr = cidr; > output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); > output->dfz[rc].broadcast = output->dfz[rc].network + > ((~(unsigned int)0) >> cidr); > output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > output->dfz[rc].broadcast = __builtin_bswap32((unsigned > int)output->dfz[rc].broadcast); > rc++; > memset(buffer, 0, 1024); > } > } > fclose(dump); > return 0; > } > > int audit_reserved(struct audit *data) { > int hijack_count = 0; > for(int i = 0; i < data->dfz_count; i++) { > unsigned int dfz_net = __builtin_bswap32((unsigned > int)data->dfz[i].network); > unsigned int dfz_bcast = __builtin_bswap32((unsigned > int)data->dfz[i].broadcast); > for(int r = 0; r < data->rc; r++) { > unsigned int resv_net = __builtin_bswap32((unsigned > int)data->reserved[r].network); > unsigned int resv_bcast = __builtin_bswap32((unsigned > int)data->reserved[r].broadcast); > if(dfz_net >= resv_net && dfz_net <= resv_bcast) { > hijack_count += ((dfz_bcast-dfz_net)+1); > char dfz_route[INET_ADDRSTRLEN] = {0}; > char resv_network[INET_ADDRSTRLEN] = {0}; > char resv_broadcast[INET_ADDRSTRLEN] = {0}; > inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &data->reserved[r].network, > resv_network, INET_ADDRSTRLEN); > inet_ntop(AF_INET, &data->reserved[r].broadcast, > resv_broadcast, INET_ADDRSTRLEN); > printf("%s/%d fell between reserved range %s -> %s [Adding > %d addresses to potential hijack]\n", > dfz_route, data->dfz[i].cidr, resv_network, > resv_broadcast, (dfz_bcast-dfz_net)+1); > } > } > for(int a = 0; a < data->ac; a++) { > unsigned int avail_net = __builtin_bswap32((unsigned > int)data->available[a].network); > unsigned int avail_bcast = __builtin_bswap32((unsigned > int)data->available[a].broadcast); > if(dfz_net >= data->available[a].network && dfz_net <= > data->available[a].broadcast) { > hijack_count += > ((data->available[a].broadcast-data->available[a].network)+1); > char dfz_route[INET_ADDRSTRLEN] = {0}; > char avail_network[INET_ADDRSTRLEN] = {0}; > char avail_broadcast[INET_ADDRSTRLEN] = {0}; > inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &avail_net, avail_network, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &avail_bcast, avail_broadcast, > INET_ADDRSTRLEN); > printf("%s/%d fell between available range %s -> %s\n", > dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); > } > } > } > printf("Found %d potentially hijacked addresses\n", hijack_count); > return 0; > } > > int main(int argc, const char * argv[]) { > struct audit data = {0}; > if(parse_dfz(BGP_DUMP, &data)) > return EXIT_FAILURE; > if(parse_afrinic_extended(AFRINIC_EXT, &data)) > return EXIT_FAILURE; > printf("Found %d total available addresses and %d total reserved > addresses\n", data.total_avail, data.total_resv); > audit_reserved(&data); > return EXIT_SUCCESS; > } > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Wed Oct 15 12:20:51 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Wed, 15 Oct 2025 15:20:51 +0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: <02e301dc3dca$83963660$8ac2a320$@afrinic.net> References: <02e301dc3dca$83963660$8ac2a320$@afrinic.net> Message-ID: Haha - Understood Ben - and as (not so subtly requested) - find below the commented code. // // main.c // AfrinicAudit // // Created by Andrew Alston on 15/10/2025. // Code is considered open use with no restrictions. // #include #include #include #include // Location of BGP Dump file *char* BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; // Location of Afrinic Extended Stats File *char* AFRINIC_EXT[256] = "/Users/aalston/audit/delegated-afrinic-extended-latest"; // Structure to contain route data *struct* routes { *unsigned* *int* network; *unsigned* *int* broadcast; *unsigned* *int* mask; *unsigned* *short* cidr; }; // Audit structure into which we parse all our data before comparison *struct* audit { *struct* routes *dfz; *int* dfz_count; *struct* routes *reserved; *int* total_resv; *int* rc; *struct* routes *available; *int* total_avail; *int* ac; }; // parse_afrinic_extended parses the extended statistics file into the audit structure // afext parameter is the file location of the afrinic extended stats file // output is a pointer to an audit restructure *int* parse_afrinic_extended(*char* *afext, *struct* audit *output) { FILE *dump = fopen(afext, "r"); *if*(!dump) *return* -1; *char* buffer[1024] = {0}; *char* *delim; output->rc = 0; // Run through the entire extended file isolating lines where the space is marked as reserved *while*(fgets(buffer, 1024, dump)) { *if*(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && strstr(buffer, "ipv4")) { output->rc++; } } // Allocate sufficient route structures for storing the reserved blocks output->reserved = calloc(output->rc, *sizeof*(*struct* routes)); *if*(!output->reserved) *return* -1; output->rc = 0; *struct* routes *resv = output->reserved; // Rewind the file pointer to the start of the file so we can re-run through the file parsing it this time rewind(dump); *while*(fgets(buffer, 1024, dump)) { // Check if this is a line matching reserved space *if*(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && strstr(buffer, "ipv4")) { // Tokenize the line such that delim becomes a pointer to the start of the network address delim = strtok(buffer, "|"); *for*(*int* i = 0; i < 3; i++) delim = strtok(*NULL*, "|"); // Convert the network address to a big endian formatted integer inet_pton(AF_INET, delim, &resv[output->rc].network); // Swap the byte ordering of the saved network address to little endian to make computations easier resv[output->rc].network = __builtin_bswap32(resv[output->rc]. network); // Jump to the next token so that delim points to the start of the number of addresses in the block delim = strtok(*NULL*, "|"); // Convert number of addresses to an integer *unsigned* *int* addr_count = atoi(delim); output->total_resv += addr_count; // Broadcast is calculated by taking the number of addresses less 1 and adding it to the little endian // network address resv[output->rc].broadcast = resv[output->rc].network +(addr_count-1); // Swap the network and broadcast back to big endian format resv[output->rc].network = __builtin_bswap32(resv[output->rc]. network); resv[output->rc].broadcast = __builtin_bswap32(resv[output->rc]. broadcast); // Calculate the subnet mask by taking a 1s compliment of the address count less 1 and flipping endianness resv[output->rc].mask = ~__builtin_bswap32((*unsigned* *int* )addr_count-1); // Increment the reserved route count. output->rc++; } } // Rewind the file pointer again rewind(dump); // Count the number of lines matching available space *while*(fgets(buffer, 1024, dump)) { *if*(strstr(buffer, "ZZ") && strstr(buffer, "available") && strstr(buffer, "ipv4")) { output->ac++; } } output->available = calloc(output->ac, *sizeof*(*struct* routes)); *if*(!output->available) *return* -1; *struct* routes *avail = output->available; // Rewind the file pointer again so we can run through the file again rewind(dump); *while*(fgets(buffer, 1024, dump)) { // Match lines for available space // Rest of the code in this function uses identical code to what we used above for reserved files, // So comments in the above apply here as well *if*(strstr(buffer, "ZZ") && strstr(buffer, "available") && strstr(buffer, "ipv4")) { delim = strtok(buffer, "|"); *for*(*int* i = 0; i < 3; i++) delim = strtok(*NULL*, "|"); inet_pton(AF_INET, delim, &avail[output->ac].network); avail[output->ac].network = __builtin_bswap32(avail[output->ac]. network); delim = strtok(*NULL*, "|"); *unsigned* *int* addr_count = atoi(delim); output->total_avail += addr_count; avail[output->ac].broadcast = avail[output->ac].network +(addr_count-1); avail[output->ac].mask = ~__builtin_bswap32((*unsigned* *int* )addr_count-1); output->ac++; } } fclose(dump); *return* 0; } // parse_dfz parses the bgp dump file *int* parse_dfz(*char* *dfz_dump, *struct* audit *output) { FILE *dump = fopen(dfz_dump, "r"); *char* buffer[1024] = {0}; *int* rc = 0, mult = 0, cidr = 0; *char* *delim; *if*(!dump) { *return* -1; } // Run through the dump file to get a count of matching routes. // The match here is made by checking for lines that start with a number between 1 and 9, contain a / and also contain a . // This was the easiest way to match lines in the BGP dump from a juniper *while*(fgets(buffer, 1024, dump)) { *if*(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") && strchr(buffer, '.')) { rc++; } } output->dfz = calloc(rc, *sizeof*(*struct* routes)); output->dfz_count = rc; *if*(!output->dfz) { *return* -1; } // Rewind the file pointer to run through again rewind(dump); rc = 0; *while*(fgets(buffer, 1024, dump)) { // Match lines that start with a number between 1 and 9 *if*(buffer[0] >= '1' && buffer[0] <= '9') { cidr = 0; // Tokenize to get the CIDR deliminator delim = strtok(buffer, "/"); delim = strtok(*NULL*, "/"); // If there is no CIDR deliminator, skip this line after resetting the buffer *if*(!delim) { memset(buffer, 0, 1024); *continue*; } // This code is essentially a manual ascii to integer to calculate the CIDR from the text mult = 1; *for*(*int* i = 0; i < 3; i++) { *if*(delim[i] >= '0' && delim[i] <= '9') { cidr = cidr * mult+(9-('9'-delim[i])); mult*=10; } } // Check if the line contains a . - if it doesnt the line is skipped, this avoids IPv6 lines // in the BGP dump delim = strchr(buffer, '.'); *if*(!delim) { memset(buffer, 0, 1024); *continue*; } // Save the CIDR output->dfz[rc].cidr = cidr; // Save the network in big endian format inet_pton(AF_INET, buffer, &output->dfz[rc].network); output->dfz[rc].cidr = cidr; // Swap the network to little endian format output->dfz[rc].network = __builtin_bswap32((*unsigned* *int* )output->dfz[rc].network); // Calculate the subnet mask using a 1s compliment of zero shifted by 32 minus the CIDR bits output->dfz[rc].mask = (~(*unsigned* *int*)0) << (32-cidr); // Calculate the broadcast by adding a 1s compliment of zero shifted right by the CIDR output->dfz[rc].broadcast = output->dfz[rc].network + ((~( *unsigned* *int*)0) >> cidr); // Convert the network and broadcast back to big endian format output->dfz[rc].network = __builtin_bswap32((*unsigned* *int* )output->dfz[rc].network); output->dfz[rc].broadcast = __builtin_bswap32((*unsigned* *int* )output->dfz[rc].broadcast); rc++; memset(buffer, 0, 1024); } } fclose(dump); *return* 0; } // audit_reserved uses a pre-populated audit structure to audit the afrinic reserved and available address // space against the routes in the DFZ dump file *int* audit_reserved(*struct* audit *data) { *int* hijack_count = 0; *int* prefix_count = 0; // Cycle through all the routes in the DFZ *for*(*int* i = 0; i < data->dfz_count; i++) { // Get little endian routes for the DFZ network and broadcast *unsigned* *int* dfz_net = __builtin_bswap32((*unsigned* *int* )data->dfz[i].network); *unsigned* *int* dfz_bcast = __builtin_bswap32((*unsigned* *int* )data->dfz[i].broadcast); // Cycle through the reserved routes in an inner loop *for*(*int* r = 0; r < data->rc; r++) { // Get the little endian versions of the reserved network and broadcasts *unsigned* *int* resv_net = __builtin_bswap32((*unsigned* *int* )data->reserved[r].network); *unsigned* *int* resv_bcast = __builtin_bswap32((*unsigned* *int*)data->reserved[r].broadcast); // If the DFZ network in little endian format is greater than or equal to the reserved network // and less than or equal to the reserved broadcast - the route falls in the reserved range *if*(dfz_net >= resv_net && dfz_net <= resv_bcast) { // Add to the hijack count using an address count calculated by subtracting the // dfz network address from the dfz broadcast address hijack_count += ((dfz_bcast-dfz_net)+1); prefix_count++; *char* dfz_route[INET_ADDRSTRLEN] = {0}; *char* resv_network[INET_ADDRSTRLEN] = {0}; *char* resv_broadcast[INET_ADDRSTRLEN] = {0}; // Convert the numeric networks and broadcast addresses to strings for printing inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, INET_ADDRSTRLEN); inet_ntop(AF_INET, &data->reserved[r].network, resv_network, INET_ADDRSTRLEN); inet_ntop(AF_INET, &data->reserved[r].broadcast, resv_broadcast, INET_ADDRSTRLEN); // Print potential hijacked routes in the reserved range printf("%s/%d fell between reserved range %s -> %s [Adding %d addresses to potential hijack]\n", dfz_route, data->dfz[i].cidr, resv_network, resv_broadcast, (dfz_bcast-dfz_net)+1); } } // Comments for the inner loop for reserved range apply equally to the below inner loop which // processes against available routes in the afrinic extended file *for*(*int* a = 0; a < data->ac; a++) { *unsigned* *int* avail_net = __builtin_bswap32((*unsigned* *int* )data->available[a].network); *unsigned* *int* avail_bcast = __builtin_bswap32((*unsigned* *int*)data->available[a].broadcast); *if*(dfz_net >= data->available[a].network && dfz_net <= data-> available[a].broadcast) { hijack_count += ((data->available[a].broadcast-data-> available[a].network)+1); prefix_count++; *char* dfz_route[INET_ADDRSTRLEN] = {0}; *char* avail_network[INET_ADDRSTRLEN] = {0}; *char* avail_broadcast[INET_ADDRSTRLEN] = {0}; inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, INET_ADDRSTRLEN); inet_ntop(AF_INET, &avail_net, avail_network, INET_ADDRSTRLEN); inet_ntop(AF_INET, &avail_bcast, avail_broadcast, INET_ADDRSTRLEN); printf("%s/%d fell between available range %s -> %s\n", dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); } } } printf("Found %d potentially hijacked addresses from %d prefixes\n", hijack_count, prefix_count); *return* 0; } *int* main(*int* argc, *const* *char* * argv[]) { *struct* audit data = {0}; // Call the DFZ file parser, expecting a zero return if all is well *if*(parse_dfz(BGP_DUMP, &data)) *return* EXIT_FAILURE; // Call the afrinic extended parser, expecting a zero return if all is well *if*(parse_afrinic_extended(AFRINIC_EXT, &data)) *return* EXIT_FAILURE; // Print the total available and reserved addresses found by the afrinic extended parser printf("Found %d total available addresses and %d total reserved addresses\n", data.total_avail, data.total_resv); // Run the audit audit_reserved(&data); *return* EXIT_SUCCESS; } On Wed, Oct 15, 2025 at 2:55?PM wrote: > This is great Andrew. I feel like we should have more of this sort of > thing and perhaps an IP address research hackathon will be a great idea. > > > > Your c is pretty good, I will give you a tip though. > > > > 2 useful features of c are to use // or /* */ to insert comments in the > code > > e.g. > > // This is a comment > > Or > > /* This is a comment*/ > > > > The comments aren?t compiled in the code so you can write anything you > like. Using comments like this is really helpful when sharing code with > others, to help them understand it? > > > > > > ??? > > > > *From:* Andrew Alston > *Sent:* 15 October 2025 14:41 > *To:* RPD > *Subject:* [rpd] Reserved Space/Available Space and potential hijacking > > > > Hi Guys, > > > > So - Firstly a few notes on using the code I'm going to paste below. > > > > I created the BGP dump file on a juniper router by running a "show route > protocol bgp | save bgp.dump.txt" and then copying that dump file to my > local system from the Juniper router. Note - this produces a roughly > 400meg file on a full table router and it takes quite a while to run the > command. > > Then - I used the delegated-afrinic-extended-latest file downloaded from > the stats ftp server. > > > > In the code below - if you wish to run similar - change the char > BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match the > pathing to the relevant files. > > > > Note that there is some weirdness in this code to deal with endianness - > and I will openly admit its not the cleanest (or probably most efficient) > code - but it does work and I've verified the results. > > > > I've pasted the code below the results section. > > > > So - first the results: > > > > Found 824064 total available addresses and 4482304 total reserved addresses > 41.57.124.0/22 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 1024 addresses to potential hijack] > 41.57.124.0/23 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 512 addresses to potential hijack] > 41.57.124.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.125.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.126.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.127.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.77.64.0/21 fell between reserved range 41.77.64.0 -> 41.77.71.255 > [Adding 2048 addresses to potential hijack] > 41.138.192.0/24 fell between reserved range 41.138.192.0 -> > 41.138.223.255 [Adding 256 addresses to potential hijack] > 41.204.224.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.225.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.226.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.227.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.228.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.229.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.230.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.231.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.232.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.233.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.234.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.235.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.236.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.237.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.238.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.239.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.240.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.241.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.242.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.243.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.244.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.245.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.246.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.247.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.248.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.249.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.250.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.251.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.254.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.255.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.205.224.0/19 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 8192 addresses to potential hijack] > 41.205.225.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.232.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.234.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.235.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.237.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.238.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.239.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.220.48.0/20 fell between reserved range 41.220.48.0 -> 41.220.63.255 > [Adding 4096 addresses to potential hijack] > 80.88.6.0/24 fell between reserved range 80.88.6.0 -> 80.88.6.255 [Adding > 256 addresses to potential hijack] > 102.128.74.0/24 fell between reserved range 102.128.72.0 -> > 102.128.75.255 [Adding 256 addresses to potential hijack] > 102.135.164.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.135.165.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.135.166.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.219.128.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.219.129.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.219.130.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.221.148.0/22 fell between reserved range 102.221.144.0 -> > 102.221.151.255 [Adding 1024 addresses to potential hijack] > 156.0.254.0/24 fell between reserved range 156.0.254.0 -> 156.0.254.255 > [Adding 256 addresses to potential hijack] > 160.119.208.0/24 fell between reserved range 160.119.208.0 -> > 160.119.211.255 [Adding 256 addresses to potential hijack] > 160.119.209.0/24 fell between reserved range 160.119.208.0 -> > 160.119.211.255 [Adding 256 addresses to potential hijack] > 164.160.192.0/21 fell between reserved range 164.160.192.0 -> > 164.160.223.255 [Adding 2048 addresses to potential hijack] > 169.255.164.0/22 fell between reserved range 169.255.164.0 -> > 169.255.167.255 [Adding 1024 addresses to potential hijack] > 193.188.7.0/24 fell between reserved range 193.188.7.0 -> 193.188.7.255 > [Adding 256 addresses to potential hijack] > 196.13.203.0/24 fell between reserved range 196.13.203.0 -> > 196.13.203.255 [Adding 256 addresses to potential hijack] > 196.20.60.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.20.61.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.20.62.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.41.74.0/24 fell between reserved range 196.41.74.0 -> 196.41.74.255 > [Adding 256 addresses to potential hijack] > 196.43.252.0/24 fell between reserved range 196.43.252.0 -> > 196.43.252.255 [Adding 256 addresses to potential hijack] > 196.46.18.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 > [Adding 256 addresses to potential hijack] > 196.46.19.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 > [Adding 256 addresses to potential hijack] > 196.46.152.0/24 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.153.0/24 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.154.0/23 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 512 addresses to potential hijack] > 196.50.21.0/24 fell between reserved range 196.50.21.0 -> 196.50.21.255 > [Adding 256 addresses to potential hijack] > 196.53.113.0/24 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 256 addresses to potential hijack] > 196.54.72.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 512 addresses to potential hijack] > 196.55.102.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 512 addresses to potential hijack] > 196.63.243.0/24 fell between reserved range 196.62.0.0 -> 196.63.255.255 > [Adding 256 addresses to potential hijack] > 196.195.4.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 > [Adding 256 addresses to potential hijack] > 196.195.15.0/24 fell between reserved range 196.194.0.0 -> > 196.195.255.255 [Adding 256 addresses to potential hijack] > 196.195.253.0/24 fell between reserved range 196.194.0.0 -> > 196.195.255.255 [Adding 256 addresses to potential hijack] > 197.157.200.0/22 fell between reserved range 197.157.200.0 -> > 197.157.203.255 [Adding 1024 addresses to potential hijack] > 197.231.248.0/22 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 1024 addresses to potential hijack] > 197.231.248.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.249.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.250.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.251.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.234.208.0/24 fell between reserved range 197.234.208.0 -> > 197.234.215.255 [Adding 256 addresses to potential hijack] > 212.12.224.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.225.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.226.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.227.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.229.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.231.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.232.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.233.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.234.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.235.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.236.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.237.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.238.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.239.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.240.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.241.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.242.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.243.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.244.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.245.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.246.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.247.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.248.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.249.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.250.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.251.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.252.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.254.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.255.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > Found 50176 potentially hijacked addresses > > > > --- Below here is the code (I didn't know if I could send attachments to > the RPD list so I just pasted the code straight) --- > > > > // > // main.c > // AfrinicAudit > // > // Created by Andrew Alston on 15/10/2025. > // Code is considered open use with no restrictions. > // > > #include > #include > #include > #include > > char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; > char AFRINIC_EXT[256] = > "/Users/aalston/audit/delegated-afrinic-extended-latest"; > > struct routes { > unsigned int network; > unsigned int broadcast; > unsigned int mask; > unsigned short cidr; > }; > > struct audit { > struct routes *dfz; > int dfz_count; > struct routes *reserved; > int total_resv; > int rc; > struct routes *available; > int total_avail; > int ac; > }; > > int parse_afrinic_extended(char *afext, struct audit *output) { > FILE *dump = fopen(afext, "r"); > if(!dump) > return -1; > char buffer[1024] = {0}; > char *delim; > output->rc = 0; > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > output->rc++; > } > } > output->reserved = calloc(output->rc, sizeof(struct routes)); > if(!output->reserved) > return -1; > output->rc = 0; > struct routes *resv = output->reserved; > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > delim = strtok(buffer, "|"); > for(int i = 0; i < 3; i++) > delim = strtok(NULL, "|"); > inet_pton(AF_INET, delim, &resv[output->rc].network); > resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > delim = strtok(NULL, "|"); > unsigned int addr_count = atoi(delim); > output->total_resv += addr_count; > resv[output->rc].broadcast = > resv[output->rc].network+(addr_count-1); > resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > resv[output->rc].broadcast = > __builtin_bswap32(resv[output->rc].broadcast); > resv[output->rc].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > output->rc++; > } > } > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > output->ac++; > } > } > output->available = calloc(output->ac, sizeof(struct routes)); > if(!output->available) > return -1; > struct routes *avail = output->available; > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > delim = strtok(buffer, "|"); > for(int i = 0; i < 3; i++) > delim = strtok(NULL, "|"); > inet_pton(AF_INET, delim, &avail[output->ac].network); > avail[output->ac].network = > __builtin_bswap32(avail[output->ac].network); > delim = strtok(NULL, "|"); > unsigned int addr_count = atoi(delim); > output->total_avail += addr_count; > avail[output->ac].broadcast = > avail[output->ac].network+(addr_count-1); > avail[output->ac].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > output->ac++; > } > } > fclose(dump); > return 0; > } > > int parse_dfz(char *dfz_dump, struct audit *output) { > FILE *dump = fopen(dfz_dump, "r"); > char buffer[1024] = {0}; > int rc = 0, mult = 0, cidr = 0; > char *delim; > if(!dump) { > return -1; > } > while(fgets(buffer, 1024, dump)) { > if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") && > strchr(buffer, '.')) { > rc++; > } > } > output->dfz = calloc(rc, sizeof(struct routes)); > output->dfz_count = rc; > if(!output->dfz) { > return -1; > } > rewind(dump); > rc = 0; > while(fgets(buffer, 1024, dump)) { > if(buffer[0] >= '1' && buffer[0] <= '9') { > cidr = 0; > delim = strtok(buffer, "/"); > delim = strtok(NULL, "/"); > if(!delim) { > memset(buffer, 0, 1024); > continue; > } > mult = 1; > for(int i = 0; i < 3; i++) { > if(delim[i] >= '0' && delim[i] <= '9') { > cidr = cidr * mult+(9-('9'-delim[i])); > mult*=10; > } > } > delim = strchr(buffer, '.'); > if(!delim) { > memset(buffer, 0, 1024); > continue; > } > output->dfz[rc].cidr = cidr; > inet_pton(AF_INET, buffer, &output->dfz[rc].network); > output->dfz[rc].cidr = cidr; > output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); > output->dfz[rc].broadcast = output->dfz[rc].network + > ((~(unsigned int)0) >> cidr); > output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > output->dfz[rc].broadcast = __builtin_bswap32((unsigned > int)output->dfz[rc].broadcast); > rc++; > memset(buffer, 0, 1024); > } > } > fclose(dump); > return 0; > } > > int audit_reserved(struct audit *data) { > int hijack_count = 0; > for(int i = 0; i < data->dfz_count; i++) { > unsigned int dfz_net = __builtin_bswap32((unsigned > int)data->dfz[i].network); > unsigned int dfz_bcast = __builtin_bswap32((unsigned > int)data->dfz[i].broadcast); > for(int r = 0; r < data->rc; r++) { > unsigned int resv_net = __builtin_bswap32((unsigned > int)data->reserved[r].network); > unsigned int resv_bcast = __builtin_bswap32((unsigned > int)data->reserved[r].broadcast); > if(dfz_net >= resv_net && dfz_net <= resv_bcast) { > hijack_count += ((dfz_bcast-dfz_net)+1); > char dfz_route[INET_ADDRSTRLEN] = {0}; > char resv_network[INET_ADDRSTRLEN] = {0}; > char resv_broadcast[INET_ADDRSTRLEN] = {0}; > inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &data->reserved[r].network, > resv_network, INET_ADDRSTRLEN); > inet_ntop(AF_INET, &data->reserved[r].broadcast, > resv_broadcast, INET_ADDRSTRLEN); > printf("%s/%d fell between reserved range %s -> %s [Adding > %d addresses to potential hijack]\n", > dfz_route, data->dfz[i].cidr, resv_network, > resv_broadcast, (dfz_bcast-dfz_net)+1); > } > } > for(int a = 0; a < data->ac; a++) { > unsigned int avail_net = __builtin_bswap32((unsigned > int)data->available[a].network); > unsigned int avail_bcast = __builtin_bswap32((unsigned > int)data->available[a].broadcast); > if(dfz_net >= data->available[a].network && dfz_net <= > data->available[a].broadcast) { > hijack_count += > ((data->available[a].broadcast-data->available[a].network)+1); > char dfz_route[INET_ADDRSTRLEN] = {0}; > char avail_network[INET_ADDRSTRLEN] = {0}; > char avail_broadcast[INET_ADDRSTRLEN] = {0}; > inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &avail_net, avail_network, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &avail_bcast, avail_broadcast, > INET_ADDRSTRLEN); > printf("%s/%d fell between available range %s -> %s\n", > dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); > } > } > } > printf("Found %d potentially hijacked addresses\n", hijack_count); > return 0; > } > > int main(int argc, const char * argv[]) { > struct audit data = {0}; > if(parse_dfz(BGP_DUMP, &data)) > return EXIT_FAILURE; > if(parse_afrinic_extended(AFRINIC_EXT, &data)) > return EXIT_FAILURE; > printf("Found %d total available addresses and %d total reserved > addresses\n", data.total_avail, data.total_resv); > audit_reserved(&data); > return EXIT_SUCCESS; > } > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Wed Oct 15 12:21:43 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Wed, 15 Oct 2025 15:21:43 +0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: References: <02e301dc3dca$83963660$8ac2a320$@afrinic.net> Message-ID: I haven't bothered to put this on github yet, will try and find the time to do so later and will share the link. Thanks Andrew On Wed, Oct 15, 2025 at 3:17?PM Noah wrote: > Hi Andrew > > In addition to Ben's comment, please share the link to the github/repo of > the code assuming it's public. > > Cheers, > *.**/noah* > > > > On Wed, Oct 15, 2025 at 3:06?PM ben.roberts--- via RPD > wrote: > >> This is great Andrew. I feel like we should have more of this sort of >> thing and perhaps an IP address research hackathon will be a great idea. >> >> >> >> Your c is pretty good, I will give you a tip though. >> >> >> >> 2 useful features of c are to use // or /* */ to insert comments in the >> code >> >> e.g. >> >> // This is a comment >> >> Or >> >> /* This is a comment*/ >> >> >> >> The comments aren?t compiled in the code so you can write anything you >> like. Using comments like this is really helpful when sharing code with >> others, to help them understand it? >> >> >> >> >> >> ??? >> >> >> >> *From:* Andrew Alston >> *Sent:* 15 October 2025 14:41 >> *To:* RPD >> *Subject:* [rpd] Reserved Space/Available Space and potential hijacking >> >> >> >> Hi Guys, >> >> >> >> So - Firstly a few notes on using the code I'm going to paste below. >> >> >> >> I created the BGP dump file on a juniper router by running a "show route >> protocol bgp | save bgp.dump.txt" and then copying that dump file to my >> local system from the Juniper router. Note - this produces a roughly >> 400meg file on a full table router and it takes quite a while to run the >> command. >> >> Then - I used the delegated-afrinic-extended-latest file downloaded from >> the stats ftp server. >> >> >> >> In the code below - if you wish to run similar - change the char >> BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match the >> pathing to the relevant files. >> >> >> >> Note that there is some weirdness in this code to deal with endianness - >> and I will openly admit its not the cleanest (or probably most efficient) >> code - but it does work and I've verified the results. >> >> >> >> I've pasted the code below the results section. >> >> >> >> So - first the results: >> >> >> >> Found 824064 total available addresses and 4482304 total reserved >> addresses >> 41.57.124.0/22 fell between reserved range 41.57.124.0 -> 41.57.127.255 >> [Adding 1024 addresses to potential hijack] >> 41.57.124.0/23 fell between reserved range 41.57.124.0 -> 41.57.127.255 >> [Adding 512 addresses to potential hijack] >> 41.57.124.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 >> [Adding 256 addresses to potential hijack] >> 41.57.125.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 >> [Adding 256 addresses to potential hijack] >> 41.57.126.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 >> [Adding 256 addresses to potential hijack] >> 41.57.127.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 >> [Adding 256 addresses to potential hijack] >> 41.77.64.0/21 fell between reserved range 41.77.64.0 -> 41.77.71.255 >> [Adding 2048 addresses to potential hijack] >> 41.138.192.0/24 fell between reserved range 41.138.192.0 -> >> 41.138.223.255 [Adding 256 addresses to potential hijack] >> 41.204.224.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.225.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.226.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.227.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.228.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.229.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.230.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.231.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.232.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.233.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.234.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.235.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.236.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.237.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.238.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.239.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.240.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.241.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.242.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.243.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.244.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.245.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.246.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.247.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.248.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.249.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.250.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.251.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.254.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.204.255.0/24 fell between reserved range 41.204.224.0 -> >> 41.204.255.255 [Adding 256 addresses to potential hijack] >> 41.205.224.0/19 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 8192 addresses to potential hijack] >> 41.205.225.0/24 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 256 addresses to potential hijack] >> 41.205.232.0/24 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 256 addresses to potential hijack] >> 41.205.234.0/24 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 256 addresses to potential hijack] >> 41.205.235.0/24 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 256 addresses to potential hijack] >> 41.205.237.0/24 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 256 addresses to potential hijack] >> 41.205.238.0/24 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 256 addresses to potential hijack] >> 41.205.239.0/24 fell between reserved range 41.205.224.0 -> >> 41.205.255.255 [Adding 256 addresses to potential hijack] >> 41.220.48.0/20 fell between reserved range 41.220.48.0 -> 41.220.63.255 >> [Adding 4096 addresses to potential hijack] >> 80.88.6.0/24 fell between reserved range 80.88.6.0 -> 80.88.6.255 >> [Adding 256 addresses to potential hijack] >> 102.128.74.0/24 fell between reserved range 102.128.72.0 -> >> 102.128.75.255 [Adding 256 addresses to potential hijack] >> 102.135.164.0/24 fell between reserved range 102.135.164.0 -> >> 102.135.167.255 [Adding 256 addresses to potential hijack] >> 102.135.165.0/24 fell between reserved range 102.135.164.0 -> >> 102.135.167.255 [Adding 256 addresses to potential hijack] >> 102.135.166.0/24 fell between reserved range 102.135.164.0 -> >> 102.135.167.255 [Adding 256 addresses to potential hijack] >> 102.219.128.0/24 fell between reserved range 102.219.128.0 -> >> 102.219.131.255 [Adding 256 addresses to potential hijack] >> 102.219.129.0/24 fell between reserved range 102.219.128.0 -> >> 102.219.131.255 [Adding 256 addresses to potential hijack] >> 102.219.130.0/24 fell between reserved range 102.219.128.0 -> >> 102.219.131.255 [Adding 256 addresses to potential hijack] >> 102.221.148.0/22 fell between reserved range 102.221.144.0 -> >> 102.221.151.255 [Adding 1024 addresses to potential hijack] >> 156.0.254.0/24 fell between reserved range 156.0.254.0 -> 156.0.254.255 >> [Adding 256 addresses to potential hijack] >> 160.119.208.0/24 fell between reserved range 160.119.208.0 -> >> 160.119.211.255 [Adding 256 addresses to potential hijack] >> 160.119.209.0/24 fell between reserved range 160.119.208.0 -> >> 160.119.211.255 [Adding 256 addresses to potential hijack] >> 164.160.192.0/21 fell between reserved range 164.160.192.0 -> >> 164.160.223.255 [Adding 2048 addresses to potential hijack] >> 169.255.164.0/22 fell between reserved range 169.255.164.0 -> >> 169.255.167.255 [Adding 1024 addresses to potential hijack] >> 193.188.7.0/24 fell between reserved range 193.188.7.0 -> 193.188.7.255 >> [Adding 256 addresses to potential hijack] >> 196.13.203.0/24 fell between reserved range 196.13.203.0 -> >> 196.13.203.255 [Adding 256 addresses to potential hijack] >> 196.20.60.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 >> [Adding 256 addresses to potential hijack] >> 196.20.61.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 >> [Adding 256 addresses to potential hijack] >> 196.20.62.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 >> [Adding 256 addresses to potential hijack] >> 196.41.74.0/24 fell between reserved range 196.41.74.0 -> 196.41.74.255 >> [Adding 256 addresses to potential hijack] >> 196.43.252.0/24 fell between reserved range 196.43.252.0 -> >> 196.43.252.255 [Adding 256 addresses to potential hijack] >> 196.46.18.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 >> [Adding 256 addresses to potential hijack] >> 196.46.19.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 >> [Adding 256 addresses to potential hijack] >> 196.46.152.0/24 fell between reserved range 196.46.152.0 -> >> 196.46.159.255 [Adding 256 addresses to potential hijack] >> 196.46.153.0/24 fell between reserved range 196.46.152.0 -> >> 196.46.159.255 [Adding 256 addresses to potential hijack] >> 196.46.154.0/23 fell between reserved range 196.46.152.0 -> >> 196.46.159.255 [Adding 512 addresses to potential hijack] >> 196.50.21.0/24 fell between reserved range 196.50.21.0 -> 196.50.21.255 >> [Adding 256 addresses to potential hijack] >> 196.53.113.0/24 fell between reserved range 196.52.0.0 -> 196.55.255.255 >> [Adding 256 addresses to potential hijack] >> 196.54.72.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 >> [Adding 512 addresses to potential hijack] >> 196.55.102.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 >> [Adding 512 addresses to potential hijack] >> 196.63.243.0/24 fell between reserved range 196.62.0.0 -> 196.63.255.255 >> [Adding 256 addresses to potential hijack] >> 196.195.4.0/24 fell between reserved range 196.194.0.0 -> >> 196.195.255.255 [Adding 256 addresses to potential hijack] >> 196.195.15.0/24 fell between reserved range 196.194.0.0 -> >> 196.195.255.255 [Adding 256 addresses to potential hijack] >> 196.195.253.0/24 fell between reserved range 196.194.0.0 -> >> 196.195.255.255 [Adding 256 addresses to potential hijack] >> 197.157.200.0/22 fell between reserved range 197.157.200.0 -> >> 197.157.203.255 [Adding 1024 addresses to potential hijack] >> 197.231.248.0/22 fell between reserved range 197.231.248.0 -> >> 197.231.251.255 [Adding 1024 addresses to potential hijack] >> 197.231.248.0/24 fell between reserved range 197.231.248.0 -> >> 197.231.251.255 [Adding 256 addresses to potential hijack] >> 197.231.249.0/24 fell between reserved range 197.231.248.0 -> >> 197.231.251.255 [Adding 256 addresses to potential hijack] >> 197.231.250.0/24 fell between reserved range 197.231.248.0 -> >> 197.231.251.255 [Adding 256 addresses to potential hijack] >> 197.231.251.0/24 fell between reserved range 197.231.248.0 -> >> 197.231.251.255 [Adding 256 addresses to potential hijack] >> 197.234.208.0/24 fell between reserved range 197.234.208.0 -> >> 197.234.215.255 [Adding 256 addresses to potential hijack] >> 212.12.224.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.225.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.226.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.227.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.229.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.231.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.232.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.233.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.234.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.235.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.236.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.237.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.238.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.239.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.240.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.241.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.242.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.243.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.244.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.245.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.246.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.247.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.248.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.249.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.250.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.251.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.252.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.254.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> 212.12.255.0/24 fell between reserved range 212.12.224.0 -> >> 212.12.255.255 [Adding 256 addresses to potential hijack] >> Found 50176 potentially hijacked addresses >> >> >> >> --- Below here is the code (I didn't know if I could send attachments to >> the RPD list so I just pasted the code straight) --- >> >> >> >> // >> // main.c >> // AfrinicAudit >> // >> // Created by Andrew Alston on 15/10/2025. >> // Code is considered open use with no restrictions. >> // >> >> #include >> #include >> #include >> #include >> >> char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; >> char AFRINIC_EXT[256] = >> "/Users/aalston/audit/delegated-afrinic-extended-latest"; >> >> struct routes { >> unsigned int network; >> unsigned int broadcast; >> unsigned int mask; >> unsigned short cidr; >> }; >> >> struct audit { >> struct routes *dfz; >> int dfz_count; >> struct routes *reserved; >> int total_resv; >> int rc; >> struct routes *available; >> int total_avail; >> int ac; >> }; >> >> int parse_afrinic_extended(char *afext, struct audit *output) { >> FILE *dump = fopen(afext, "r"); >> if(!dump) >> return -1; >> char buffer[1024] = {0}; >> char *delim; >> output->rc = 0; >> while(fgets(buffer, 1024, dump)) { >> if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && >> strstr(buffer, "ipv4")) { >> output->rc++; >> } >> } >> output->reserved = calloc(output->rc, sizeof(struct routes)); >> if(!output->reserved) >> return -1; >> output->rc = 0; >> struct routes *resv = output->reserved; >> rewind(dump); >> while(fgets(buffer, 1024, dump)) { >> if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && >> strstr(buffer, "ipv4")) { >> delim = strtok(buffer, "|"); >> for(int i = 0; i < 3; i++) >> delim = strtok(NULL, "|"); >> inet_pton(AF_INET, delim, &resv[output->rc].network); >> resv[output->rc].network = >> __builtin_bswap32(resv[output->rc].network); >> delim = strtok(NULL, "|"); >> unsigned int addr_count = atoi(delim); >> output->total_resv += addr_count; >> resv[output->rc].broadcast = >> resv[output->rc].network+(addr_count-1); >> resv[output->rc].network = >> __builtin_bswap32(resv[output->rc].network); >> resv[output->rc].broadcast = >> __builtin_bswap32(resv[output->rc].broadcast); >> resv[output->rc].mask = ~__builtin_bswap32((unsigned >> int)addr_count-1); >> output->rc++; >> } >> } >> rewind(dump); >> while(fgets(buffer, 1024, dump)) { >> if(strstr(buffer, "ZZ") && strstr(buffer, "available") && >> strstr(buffer, "ipv4")) { >> output->ac++; >> } >> } >> output->available = calloc(output->ac, sizeof(struct routes)); >> if(!output->available) >> return -1; >> struct routes *avail = output->available; >> rewind(dump); >> while(fgets(buffer, 1024, dump)) { >> if(strstr(buffer, "ZZ") && strstr(buffer, "available") && >> strstr(buffer, "ipv4")) { >> delim = strtok(buffer, "|"); >> for(int i = 0; i < 3; i++) >> delim = strtok(NULL, "|"); >> inet_pton(AF_INET, delim, &avail[output->ac].network); >> avail[output->ac].network = >> __builtin_bswap32(avail[output->ac].network); >> delim = strtok(NULL, "|"); >> unsigned int addr_count = atoi(delim); >> output->total_avail += addr_count; >> avail[output->ac].broadcast = >> avail[output->ac].network+(addr_count-1); >> avail[output->ac].mask = ~__builtin_bswap32((unsigned >> int)addr_count-1); >> output->ac++; >> } >> } >> fclose(dump); >> return 0; >> } >> >> int parse_dfz(char *dfz_dump, struct audit *output) { >> FILE *dump = fopen(dfz_dump, "r"); >> char buffer[1024] = {0}; >> int rc = 0, mult = 0, cidr = 0; >> char *delim; >> if(!dump) { >> return -1; >> } >> while(fgets(buffer, 1024, dump)) { >> if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") && >> strchr(buffer, '.')) { >> rc++; >> } >> } >> output->dfz = calloc(rc, sizeof(struct routes)); >> output->dfz_count = rc; >> if(!output->dfz) { >> return -1; >> } >> rewind(dump); >> rc = 0; >> while(fgets(buffer, 1024, dump)) { >> if(buffer[0] >= '1' && buffer[0] <= '9') { >> cidr = 0; >> delim = strtok(buffer, "/"); >> delim = strtok(NULL, "/"); >> if(!delim) { >> memset(buffer, 0, 1024); >> continue; >> } >> mult = 1; >> for(int i = 0; i < 3; i++) { >> if(delim[i] >= '0' && delim[i] <= '9') { >> cidr = cidr * mult+(9-('9'-delim[i])); >> mult*=10; >> } >> } >> delim = strchr(buffer, '.'); >> if(!delim) { >> memset(buffer, 0, 1024); >> continue; >> } >> output->dfz[rc].cidr = cidr; >> inet_pton(AF_INET, buffer, &output->dfz[rc].network); >> output->dfz[rc].cidr = cidr; >> output->dfz[rc].network = __builtin_bswap32((unsigned >> int)output->dfz[rc].network); >> output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); >> output->dfz[rc].broadcast = output->dfz[rc].network + >> ((~(unsigned int)0) >> cidr); >> output->dfz[rc].network = __builtin_bswap32((unsigned >> int)output->dfz[rc].network); >> output->dfz[rc].broadcast = __builtin_bswap32((unsigned >> int)output->dfz[rc].broadcast); >> rc++; >> memset(buffer, 0, 1024); >> } >> } >> fclose(dump); >> return 0; >> } >> >> int audit_reserved(struct audit *data) { >> int hijack_count = 0; >> for(int i = 0; i < data->dfz_count; i++) { >> unsigned int dfz_net = __builtin_bswap32((unsigned >> int)data->dfz[i].network); >> unsigned int dfz_bcast = __builtin_bswap32((unsigned >> int)data->dfz[i].broadcast); >> for(int r = 0; r < data->rc; r++) { >> unsigned int resv_net = __builtin_bswap32((unsigned >> int)data->reserved[r].network); >> unsigned int resv_bcast = __builtin_bswap32((unsigned >> int)data->reserved[r].broadcast); >> if(dfz_net >= resv_net && dfz_net <= resv_bcast) { >> hijack_count += ((dfz_bcast-dfz_net)+1); >> char dfz_route[INET_ADDRSTRLEN] = {0}; >> char resv_network[INET_ADDRSTRLEN] = {0}; >> char resv_broadcast[INET_ADDRSTRLEN] = {0}; >> inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, >> INET_ADDRSTRLEN); >> inet_ntop(AF_INET, &data->reserved[r].network, >> resv_network, INET_ADDRSTRLEN); >> inet_ntop(AF_INET, &data->reserved[r].broadcast, >> resv_broadcast, INET_ADDRSTRLEN); >> printf("%s/%d fell between reserved range %s -> %s >> [Adding %d addresses to potential hijack]\n", >> dfz_route, data->dfz[i].cidr, resv_network, >> resv_broadcast, (dfz_bcast-dfz_net)+1); >> } >> } >> for(int a = 0; a < data->ac; a++) { >> unsigned int avail_net = __builtin_bswap32((unsigned >> int)data->available[a].network); >> unsigned int avail_bcast = __builtin_bswap32((unsigned >> int)data->available[a].broadcast); >> if(dfz_net >= data->available[a].network && dfz_net <= >> data->available[a].broadcast) { >> hijack_count += >> ((data->available[a].broadcast-data->available[a].network)+1); >> char dfz_route[INET_ADDRSTRLEN] = {0}; >> char avail_network[INET_ADDRSTRLEN] = {0}; >> char avail_broadcast[INET_ADDRSTRLEN] = {0}; >> inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, >> INET_ADDRSTRLEN); >> inet_ntop(AF_INET, &avail_net, avail_network, >> INET_ADDRSTRLEN); >> inet_ntop(AF_INET, &avail_bcast, avail_broadcast, >> INET_ADDRSTRLEN); >> printf("%s/%d fell between available range %s -> %s\n", >> dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); >> } >> } >> } >> printf("Found %d potentially hijacked addresses\n", hijack_count); >> return 0; >> } >> >> int main(int argc, const char * argv[]) { >> struct audit data = {0}; >> if(parse_dfz(BGP_DUMP, &data)) >> return EXIT_FAILURE; >> if(parse_afrinic_extended(AFRINIC_EXT, &data)) >> return EXIT_FAILURE; >> printf("Found %d total available addresses and %d total reserved >> addresses\n", data.total_avail, data.total_resv); >> audit_reserved(&data); >> return EXIT_SUCCESS; >> } >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Wed Oct 15 12:24:35 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Wed, 15 Oct 2025 15:24:35 +0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: References: Message-ID: Hi Fernando, It's unfortunately extremely difficult to do this - because while an ASN may be allocated by AfriNIC it could be announced from anywhere, and even in the case of where an ASN is allocated by RIPE, it may be used in Africa to announce AfriNIC space (Liquid Telecom is an example of this, where 30844 is a RIPE ASN but almost all the space under it is afrinic allocated and announced in Africa). It would be possible to extend the code I wrote to show the source ASN of the prefix's that are reserved - and then potentially to match that against other AfriNIC data to show who the ASN is owned by (if the ASN itself is allocated, in my verification I found that many of these prefix's are being announced by ASN's that are marked as available or reserved) I will see what I can do about adding that extra code at some point when I find the time. Thanks Andrew On Wed, Oct 15, 2025 at 3:14?PM Fernando Frediani wrote: > Would it be possible to get detailed information about AfriNic prefixes > that are currently being announced by different ASNs they are linked to and > potentially being used out of the Africa region as well ? That would be a > pretty interesting information to see. > > Regards > Fernando > On 10/15/2025 8:40 AM, Andrew Alston wrote: > > Hi Guys, > > So - Firstly a few notes on using the code I'm going to paste below. > > I created the BGP dump file on a juniper router by running a "show route > protocol bgp | save bgp.dump.txt" and then copying that dump file to my > local system from the Juniper router. Note - this produces a roughly > 400meg file on a full table router and it takes quite a while to run the > command. > Then - I used the delegated-afrinic-extended-latest file downloaded from > the stats ftp server. > > In the code below - if you wish to run similar - change the char > BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match the > pathing to the relevant files. > > Note that there is some weirdness in this code to deal with endianness - > and I will openly admit its not the cleanest (or probably most efficient) > code - but it does work and I've verified the results. > > I've pasted the code below the results section. > > So - first the results: > > Found 824064 total available addresses and 4482304 total reserved addresses > 41.57.124.0/22 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 1024 addresses to potential hijack] > 41.57.124.0/23 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 512 addresses to potential hijack] > 41.57.124.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.125.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.126.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.57.127.0/24 fell between reserved range 41.57.124.0 -> 41.57.127.255 > [Adding 256 addresses to potential hijack] > 41.77.64.0/21 fell between reserved range 41.77.64.0 -> 41.77.71.255 > [Adding 2048 addresses to potential hijack] > 41.138.192.0/24 fell between reserved range 41.138.192.0 -> > 41.138.223.255 [Adding 256 addresses to potential hijack] > 41.204.224.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.225.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.226.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.227.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.228.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.229.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.230.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.231.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.232.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.233.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.234.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.235.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.236.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.237.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.238.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.239.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.240.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.241.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.242.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.243.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.244.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.245.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.246.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.247.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.248.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.249.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.250.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.251.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.254.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.204.255.0/24 fell between reserved range 41.204.224.0 -> > 41.204.255.255 [Adding 256 addresses to potential hijack] > 41.205.224.0/19 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 8192 addresses to potential hijack] > 41.205.225.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.232.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.234.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.235.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.237.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.238.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.205.239.0/24 fell between reserved range 41.205.224.0 -> > 41.205.255.255 [Adding 256 addresses to potential hijack] > 41.220.48.0/20 fell between reserved range 41.220.48.0 -> 41.220.63.255 > [Adding 4096 addresses to potential hijack] > 80.88.6.0/24 fell between reserved range 80.88.6.0 -> 80.88.6.255 [Adding > 256 addresses to potential hijack] > 102.128.74.0/24 fell between reserved range 102.128.72.0 -> > 102.128.75.255 [Adding 256 addresses to potential hijack] > 102.135.164.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.135.165.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.135.166.0/24 fell between reserved range 102.135.164.0 -> > 102.135.167.255 [Adding 256 addresses to potential hijack] > 102.219.128.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.219.129.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.219.130.0/24 fell between reserved range 102.219.128.0 -> > 102.219.131.255 [Adding 256 addresses to potential hijack] > 102.221.148.0/22 fell between reserved range 102.221.144.0 -> > 102.221.151.255 [Adding 1024 addresses to potential hijack] > 156.0.254.0/24 fell between reserved range 156.0.254.0 -> 156.0.254.255 > [Adding 256 addresses to potential hijack] > 160.119.208.0/24 fell between reserved range 160.119.208.0 -> > 160.119.211.255 [Adding 256 addresses to potential hijack] > 160.119.209.0/24 fell between reserved range 160.119.208.0 -> > 160.119.211.255 [Adding 256 addresses to potential hijack] > 164.160.192.0/21 fell between reserved range 164.160.192.0 -> > 164.160.223.255 [Adding 2048 addresses to potential hijack] > 169.255.164.0/22 fell between reserved range 169.255.164.0 -> > 169.255.167.255 [Adding 1024 addresses to potential hijack] > 193.188.7.0/24 fell between reserved range 193.188.7.0 -> 193.188.7.255 > [Adding 256 addresses to potential hijack] > 196.13.203.0/24 fell between reserved range 196.13.203.0 -> > 196.13.203.255 [Adding 256 addresses to potential hijack] > 196.20.60.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.20.61.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.20.62.0/24 fell between reserved range 196.20.32.0 -> 196.20.63.255 > [Adding 256 addresses to potential hijack] > 196.41.74.0/24 fell between reserved range 196.41.74.0 -> 196.41.74.255 > [Adding 256 addresses to potential hijack] > 196.43.252.0/24 fell between reserved range 196.43.252.0 -> > 196.43.252.255 [Adding 256 addresses to potential hijack] > 196.46.18.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 > [Adding 256 addresses to potential hijack] > 196.46.19.0/24 fell between reserved range 196.46.18.0 -> 196.46.19.255 > [Adding 256 addresses to potential hijack] > 196.46.152.0/24 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.153.0/24 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 256 addresses to potential hijack] > 196.46.154.0/23 fell between reserved range 196.46.152.0 -> > 196.46.159.255 [Adding 512 addresses to potential hijack] > 196.50.21.0/24 fell between reserved range 196.50.21.0 -> 196.50.21.255 > [Adding 256 addresses to potential hijack] > 196.53.113.0/24 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 256 addresses to potential hijack] > 196.54.72.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 512 addresses to potential hijack] > 196.55.102.0/23 fell between reserved range 196.52.0.0 -> 196.55.255.255 > [Adding 512 addresses to potential hijack] > 196.63.243.0/24 fell between reserved range 196.62.0.0 -> 196.63.255.255 > [Adding 256 addresses to potential hijack] > 196.195.4.0/24 fell between reserved range 196.194.0.0 -> 196.195.255.255 > [Adding 256 addresses to potential hijack] > 196.195.15.0/24 fell between reserved range 196.194.0.0 -> > 196.195.255.255 [Adding 256 addresses to potential hijack] > 196.195.253.0/24 fell between reserved range 196.194.0.0 -> > 196.195.255.255 [Adding 256 addresses to potential hijack] > 197.157.200.0/22 fell between reserved range 197.157.200.0 -> > 197.157.203.255 [Adding 1024 addresses to potential hijack] > 197.231.248.0/22 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 1024 addresses to potential hijack] > 197.231.248.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.249.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.250.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.231.251.0/24 fell between reserved range 197.231.248.0 -> > 197.231.251.255 [Adding 256 addresses to potential hijack] > 197.234.208.0/24 fell between reserved range 197.234.208.0 -> > 197.234.215.255 [Adding 256 addresses to potential hijack] > 212.12.224.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.225.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.226.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.227.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.229.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.231.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.232.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.233.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.234.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.235.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.236.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.237.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.238.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.239.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.240.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.241.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.242.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.243.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.244.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.245.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.246.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.247.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.248.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.249.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.250.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.251.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.252.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.254.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > 212.12.255.0/24 fell between reserved range 212.12.224.0 -> > 212.12.255.255 [Adding 256 addresses to potential hijack] > Found 50176 potentially hijacked addresses > > --- Below here is the code (I didn't know if I could send attachments to > the RPD list so I just pasted the code straight) --- > > // > // main.c > // AfrinicAudit > // > // Created by Andrew Alston on 15/10/2025. > // Code is considered open use with no restrictions. > // > > #include > #include > #include > #include > > char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; > char AFRINIC_EXT[256] = > "/Users/aalston/audit/delegated-afrinic-extended-latest"; > > struct routes { > unsigned int network; > unsigned int broadcast; > unsigned int mask; > unsigned short cidr; > }; > > struct audit { > struct routes *dfz; > int dfz_count; > struct routes *reserved; > int total_resv; > int rc; > struct routes *available; > int total_avail; > int ac; > }; > > int parse_afrinic_extended(char *afext, struct audit *output) { > FILE *dump = fopen(afext, "r"); > if(!dump) > return -1; > char buffer[1024] = {0}; > char *delim; > output->rc = 0; > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > output->rc++; > } > } > output->reserved = calloc(output->rc, sizeof(struct routes)); > if(!output->reserved) > return -1; > output->rc = 0; > struct routes *resv = output->reserved; > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && > strstr(buffer, "ipv4")) { > delim = strtok(buffer, "|"); > for(int i = 0; i < 3; i++) > delim = strtok(NULL, "|"); > inet_pton(AF_INET, delim, &resv[output->rc].network); > resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > delim = strtok(NULL, "|"); > unsigned int addr_count = atoi(delim); > output->total_resv += addr_count; > resv[output->rc].broadcast = > resv[output->rc].network+(addr_count-1); > resv[output->rc].network = > __builtin_bswap32(resv[output->rc].network); > resv[output->rc].broadcast = > __builtin_bswap32(resv[output->rc].broadcast); > resv[output->rc].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > output->rc++; > } > } > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > output->ac++; > } > } > output->available = calloc(output->ac, sizeof(struct routes)); > if(!output->available) > return -1; > struct routes *avail = output->available; > rewind(dump); > while(fgets(buffer, 1024, dump)) { > if(strstr(buffer, "ZZ") && strstr(buffer, "available") && > strstr(buffer, "ipv4")) { > delim = strtok(buffer, "|"); > for(int i = 0; i < 3; i++) > delim = strtok(NULL, "|"); > inet_pton(AF_INET, delim, &avail[output->ac].network); > avail[output->ac].network = > __builtin_bswap32(avail[output->ac].network); > delim = strtok(NULL, "|"); > unsigned int addr_count = atoi(delim); > output->total_avail += addr_count; > avail[output->ac].broadcast = > avail[output->ac].network+(addr_count-1); > avail[output->ac].mask = ~__builtin_bswap32((unsigned > int)addr_count-1); > output->ac++; > } > } > fclose(dump); > return 0; > } > > int parse_dfz(char *dfz_dump, struct audit *output) { > FILE *dump = fopen(dfz_dump, "r"); > char buffer[1024] = {0}; > int rc = 0, mult = 0, cidr = 0; > char *delim; > if(!dump) { > return -1; > } > while(fgets(buffer, 1024, dump)) { > if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, "/") && > strchr(buffer, '.')) { > rc++; > } > } > output->dfz = calloc(rc, sizeof(struct routes)); > output->dfz_count = rc; > if(!output->dfz) { > return -1; > } > rewind(dump); > rc = 0; > while(fgets(buffer, 1024, dump)) { > if(buffer[0] >= '1' && buffer[0] <= '9') { > cidr = 0; > delim = strtok(buffer, "/"); > delim = strtok(NULL, "/"); > if(!delim) { > memset(buffer, 0, 1024); > continue; > } > mult = 1; > for(int i = 0; i < 3; i++) { > if(delim[i] >= '0' && delim[i] <= '9') { > cidr = cidr * mult+(9-('9'-delim[i])); > mult*=10; > } > } > delim = strchr(buffer, '.'); > if(!delim) { > memset(buffer, 0, 1024); > continue; > } > output->dfz[rc].cidr = cidr; > inet_pton(AF_INET, buffer, &output->dfz[rc].network); > output->dfz[rc].cidr = cidr; > output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); > output->dfz[rc].broadcast = output->dfz[rc].network + > ((~(unsigned int)0) >> cidr); > output->dfz[rc].network = __builtin_bswap32((unsigned > int)output->dfz[rc].network); > output->dfz[rc].broadcast = __builtin_bswap32((unsigned > int)output->dfz[rc].broadcast); > rc++; > memset(buffer, 0, 1024); > } > } > fclose(dump); > return 0; > } > > int audit_reserved(struct audit *data) { > int hijack_count = 0; > for(int i = 0; i < data->dfz_count; i++) { > unsigned int dfz_net = __builtin_bswap32((unsigned > int)data->dfz[i].network); > unsigned int dfz_bcast = __builtin_bswap32((unsigned > int)data->dfz[i].broadcast); > for(int r = 0; r < data->rc; r++) { > unsigned int resv_net = __builtin_bswap32((unsigned > int)data->reserved[r].network); > unsigned int resv_bcast = __builtin_bswap32((unsigned > int)data->reserved[r].broadcast); > if(dfz_net >= resv_net && dfz_net <= resv_bcast) { > hijack_count += ((dfz_bcast-dfz_net)+1); > char dfz_route[INET_ADDRSTRLEN] = {0}; > char resv_network[INET_ADDRSTRLEN] = {0}; > char resv_broadcast[INET_ADDRSTRLEN] = {0}; > inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &data->reserved[r].network, > resv_network, INET_ADDRSTRLEN); > inet_ntop(AF_INET, &data->reserved[r].broadcast, > resv_broadcast, INET_ADDRSTRLEN); > printf("%s/%d fell between reserved range %s -> %s [Adding > %d addresses to potential hijack]\n", > dfz_route, data->dfz[i].cidr, resv_network, > resv_broadcast, (dfz_bcast-dfz_net)+1); > } > } > for(int a = 0; a < data->ac; a++) { > unsigned int avail_net = __builtin_bswap32((unsigned > int)data->available[a].network); > unsigned int avail_bcast = __builtin_bswap32((unsigned > int)data->available[a].broadcast); > if(dfz_net >= data->available[a].network && dfz_net <= > data->available[a].broadcast) { > hijack_count += > ((data->available[a].broadcast-data->available[a].network)+1); > char dfz_route[INET_ADDRSTRLEN] = {0}; > char avail_network[INET_ADDRSTRLEN] = {0}; > char avail_broadcast[INET_ADDRSTRLEN] = {0}; > inet_ntop(AF_INET, &data->dfz[i].network, dfz_route, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &avail_net, avail_network, > INET_ADDRSTRLEN); > inet_ntop(AF_INET, &avail_bcast, avail_broadcast, > INET_ADDRSTRLEN); > printf("%s/%d fell between available range %s -> %s\n", > dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); > } > } > } > printf("Found %d potentially hijacked addresses\n", hijack_count); > return 0; > } > > int main(int argc, const char * argv[]) { > struct audit data = {0}; > if(parse_dfz(BGP_DUMP, &data)) > return EXIT_FAILURE; > if(parse_afrinic_extended(AFRINIC_EXT, &data)) > return EXIT_FAILURE; > printf("Found %d total available addresses and %d total reserved > addresses\n", data.total_avail, data.total_resv); > audit_reserved(&data); > return EXIT_SUCCESS; > } > > _______________________________________________ > RPD mailing listRPD at afrinic.nethttps://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fhfrediani at gmail.com Wed Oct 15 12:35:53 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Wed, 15 Oct 2025 09:35:53 -0300 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: References: Message-ID: <34cba83c-e08f-48d5-9815-ee9637e618ba@gmail.com> Yeah it could be, but I would say that alone is already something that can bring attention to resources because it is not what is widely expected. I would easily believe that a fair amount of space announce by other ASNs other than the one linked to it in the whois may not be what was desired or justified at the same resources were allocated. There are valid examples as you mentioned, but I would say they are the fewer. I think the most important in this context is find out if the resources are being use in Africa or not which it is slightly more complex to asses than matching with whois data. Fernando On 10/15/2025 9:24 AM, Andrew Alston wrote: > Hi Fernando, > > It's unfortunately extremely difficult to do this - because while an > ASN may be allocated by AfriNIC it could be announced from anywhere, > and even in the case of where an ASN is allocated by RIPE, it may be > used in Africa to announce AfriNIC space (Liquid Telecom is an example > of this, where 30844 is a RIPE ASN but almost all the space under it > is afrinic allocated and announced in Africa). > > It would be possible to extend the code I wrote to show the source ASN > of the prefix's?that are reserved - and then potentially to match that > against other AfriNIC data to show who the ASN is owned by (if the ASN > itself is allocated, in my verification I found that many of these > prefix's are being announced by ASN's that are marked as available or > reserved) > > I will see what I can do about adding that extra code at some point > when I find the time. > > Thanks > > Andrew > > > On Wed, Oct 15, 2025 at 3:14?PM Fernando Frediani > wrote: > > Would it be possible to get detailed information about AfriNic > prefixes that are currently being announced by different ASNs they > are linked to and potentially being used out of the Africa region > as well ? That would be a pretty interesting information to see. > > Regards > Fernando > > On 10/15/2025 8:40 AM, Andrew Alston wrote: >> Hi Guys, >> >> So - Firstly a few notes on using the code I'm going to paste below. >> >> I created the BGP dump file on a juniper router by running a >> "show route protocol bgp | save bgp.dump.txt" and then copying >> that dump file to my local system from the Juniper router.? Note >> - this produces a roughly 400meg file on a full table router and >> it takes quite a while to run the command. >> Then - I used the delegated-afrinic-extended-latest file >> downloaded from the stats ftp server. >> >> In the code below - if you wish to run similar - change the char >> BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to match >> the pathing to the relevant files. >> >> Note that there is some weirdness?in this code to deal with >> endianness - and I will openly admit its not the cleanest (or >> probably most efficient) code - but it does work and I've >> verified the results. >> >> I've pasted the code below the results section. >> >> So - first the results: >> >> Found 824064 total available addresses and 4482304 total reserved >> addresses >> 41.57.124.0/22 fell between reserved >> range 41.57.124.0 -> 41.57.127.255 [Adding 1024 addresses to >> potential hijack] >> 41.57.124.0/23 fell between reserved >> range 41.57.124.0 -> 41.57.127.255 [Adding 512 addresses to >> potential hijack] >> 41.57.124.0/24 fell between reserved >> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >> potential hijack] >> 41.57.125.0/24 fell between reserved >> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >> potential hijack] >> 41.57.126.0/24 fell between reserved >> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >> potential hijack] >> 41.57.127.0/24 fell between reserved >> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >> potential hijack] >> 41.77.64.0/21 fell between reserved range >> 41.77.64.0 -> 41.77.71.255 [Adding 2048 addresses to potential >> hijack] >> 41.138.192.0/24 fell between reserved >> range 41.138.192.0 -> 41.138.223.255 [Adding 256 addresses to >> potential hijack] >> 41.204.224.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.225.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.226.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.227.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.228.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.229.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.230.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.231.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.232.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.233.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.234.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.235.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.236.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.237.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.238.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.239.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.240.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.241.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.242.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.243.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.244.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.245.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.246.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.247.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.248.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.249.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.250.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.251.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.254.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.204.255.0/24 fell between reserved >> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >> potential hijack] >> 41.205.224.0/19 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 8192 addresses to >> potential hijack] >> 41.205.225.0/24 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >> potential hijack] >> 41.205.232.0/24 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >> potential hijack] >> 41.205.234.0/24 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >> potential hijack] >> 41.205.235.0/24 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >> potential hijack] >> 41.205.237.0/24 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >> potential hijack] >> 41.205.238.0/24 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >> potential hijack] >> 41.205.239.0/24 fell between reserved >> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >> potential hijack] >> 41.220.48.0/20 fell between reserved >> range 41.220.48.0 -> 41.220.63.255 [Adding 4096 addresses to >> potential hijack] >> 80.88.6.0/24 fell between reserved range >> 80.88.6.0 -> 80.88.6.255 [Adding 256 addresses to potential hijack] >> 102.128.74.0/24 fell between reserved >> range 102.128.72.0 -> 102.128.75.255 [Adding 256 addresses to >> potential hijack] >> 102.135.164.0/24 fell between reserved >> range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to >> potential hijack] >> 102.135.165.0/24 fell between reserved >> range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to >> potential hijack] >> 102.135.166.0/24 fell between reserved >> range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to >> potential hijack] >> 102.219.128.0/24 fell between reserved >> range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to >> potential hijack] >> 102.219.129.0/24 fell between reserved >> range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to >> potential hijack] >> 102.219.130.0/24 fell between reserved >> range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to >> potential hijack] >> 102.221.148.0/22 fell between reserved >> range 102.221.144.0 -> 102.221.151.255 [Adding 1024 addresses to >> potential hijack] >> 156.0.254.0/24 fell between reserved >> range 156.0.254.0 -> 156.0.254.255 [Adding 256 addresses to >> potential hijack] >> 160.119.208.0/24 fell between reserved >> range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to >> potential hijack] >> 160.119.209.0/24 fell between reserved >> range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to >> potential hijack] >> 164.160.192.0/21 fell between reserved >> range 164.160.192.0 -> 164.160.223.255 [Adding 2048 addresses to >> potential hijack] >> 169.255.164.0/22 fell between reserved >> range 169.255.164.0 -> 169.255.167.255 [Adding 1024 addresses to >> potential hijack] >> 193.188.7.0/24 fell between reserved >> range 193.188.7.0 -> 193.188.7.255 [Adding 256 addresses to >> potential hijack] >> 196.13.203.0/24 fell between reserved >> range 196.13.203.0 -> 196.13.203.255 [Adding 256 addresses to >> potential hijack] >> 196.20.60.0/24 fell between reserved >> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >> potential hijack] >> 196.20.61.0/24 fell between reserved >> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >> potential hijack] >> 196.20.62.0/24 fell between reserved >> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >> potential hijack] >> 196.41.74.0/24 fell between reserved >> range 196.41.74.0 -> 196.41.74.255 [Adding 256 addresses to >> potential hijack] >> 196.43.252.0/24 fell between reserved >> range 196.43.252.0 -> 196.43.252.255 [Adding 256 addresses to >> potential hijack] >> 196.46.18.0/24 fell between reserved >> range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to >> potential hijack] >> 196.46.19.0/24 fell between reserved >> range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to >> potential hijack] >> 196.46.152.0/24 fell between reserved >> range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to >> potential hijack] >> 196.46.153.0/24 fell between reserved >> range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to >> potential hijack] >> 196.46.154.0/23 fell between reserved >> range 196.46.152.0 -> 196.46.159.255 [Adding 512 addresses to >> potential hijack] >> 196.50.21.0/24 fell between reserved >> range 196.50.21.0 -> 196.50.21.255 [Adding 256 addresses to >> potential hijack] >> 196.53.113.0/24 fell between reserved >> range 196.52.0.0 -> 196.55.255.255 [Adding 256 addresses to >> potential hijack] >> 196.54.72.0/23 fell between reserved >> range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to >> potential hijack] >> 196.55.102.0/23 fell between reserved >> range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to >> potential hijack] >> 196.63.243.0/24 fell between reserved >> range 196.62.0.0 -> 196.63.255.255 [Adding 256 addresses to >> potential hijack] >> 196.195.4.0/24 fell between reserved >> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >> potential hijack] >> 196.195.15.0/24 fell between reserved >> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >> potential hijack] >> 196.195.253.0/24 fell between reserved >> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >> potential hijack] >> 197.157.200.0/22 fell between reserved >> range 197.157.200.0 -> 197.157.203.255 [Adding 1024 addresses to >> potential hijack] >> 197.231.248.0/22 fell between reserved >> range 197.231.248.0 -> 197.231.251.255 [Adding 1024 addresses to >> potential hijack] >> 197.231.248.0/24 fell between reserved >> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >> potential hijack] >> 197.231.249.0/24 fell between reserved >> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >> potential hijack] >> 197.231.250.0/24 fell between reserved >> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >> potential hijack] >> 197.231.251.0/24 fell between reserved >> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >> potential hijack] >> 197.234.208.0/24 fell between reserved >> range 197.234.208.0 -> 197.234.215.255 [Adding 256 addresses to >> potential hijack] >> 212.12.224.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.225.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.226.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.227.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.229.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.231.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.232.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.233.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.234.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.235.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.236.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.237.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.238.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.239.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.240.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.241.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.242.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.243.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.244.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.245.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.246.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.247.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.248.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.249.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.250.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.251.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.252.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.254.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> 212.12.255.0/24 fell between reserved >> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >> potential hijack] >> Found 50176 potentially hijacked addresses >> >> --- Below here is the code (I didn't know if I could send >> attachments to the RPD list so I just pasted the code straight) --- >> >> // >> // ?main.c >> // ?AfrinicAudit >> // >> // ?Created by Andrew Alston on 15/10/2025. >> // ?Code is considered open use with no restrictions. >> // >> >> #include >> #include >> #include >> #include >> >> char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; >> char AFRINIC_EXT[256] = >> "/Users/aalston/audit/delegated-afrinic-extended-latest"; >> >> struct routes { >> ? ? unsigned int network; >> ? ? unsigned int broadcast; >> ? ? unsigned int mask; >> ? ? unsigned short cidr; >> }; >> >> struct audit { >> ? ? struct routes *dfz; >> ? ? int dfz_count; >> ? ? struct routes *reserved; >> ? ? int total_resv; >> ? ? int rc; >> ? ? struct routes *available; >> ? ? int total_avail; >> ? ? int ac; >> }; >> >> int parse_afrinic_extended(char *afext, struct audit *output) { >> ? ? FILE *dump = fopen(afext, "r"); >> ? ? if(!dump) >> ? ? ? ? return -1; >> ? ? char buffer[1024] = {0}; >> ? ? char *delim; >> ? ? output->rc = 0; >> ? ? while(fgets(buffer, 1024, dump)) { >> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && >> strstr(buffer, "ipv4")) { >> ? ? ? ? ? ? output->rc++; >> ? ? ? ? } >> ? ? } >> ? ? output->reserved = calloc(output->rc, sizeof(struct routes)); >> ? ? if(!output->reserved) >> ? ? ? ? return -1; >> ? ? output->rc = 0; >> ? ? struct routes *resv = output->reserved; >> ? ? rewind(dump); >> ? ? while(fgets(buffer, 1024, dump)) { >> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && >> strstr(buffer, "ipv4")) { >> ? ? ? ? ? ? delim = strtok(buffer, "|"); >> ? ? ? ? ? ? for(int i = 0; i < 3; i++) >> ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); >> ? ? ? ? ? ? inet_pton(AF_INET, delim, &resv[output->rc].network); >> ? ? ? ? ? ? resv[output->rc].network = >> __builtin_bswap32(resv[output->rc].network); >> ? ? ? ? ? ? delim = strtok(NULL, "|"); >> ? ? ? ? ? ? unsigned int addr_count = atoi(delim); >> ? ? ? ? ? ? output->total_resv += addr_count; >> ? ? ? ? ? ? resv[output->rc].broadcast = >> resv[output->rc].network+(addr_count-1); >> ? ? ? ? ? ? resv[output->rc].network = >> __builtin_bswap32(resv[output->rc].network); >> ? ? ? ? ? ? resv[output->rc].broadcast = >> __builtin_bswap32(resv[output->rc].broadcast); >> ? ? ? ? ? ? resv[output->rc].mask = ~__builtin_bswap32((unsigned >> int)addr_count-1); >> ? ? ? ? ? ? output->rc++; >> ? ? ? ? } >> ? ? } >> ? ? rewind(dump); >> ? ? while(fgets(buffer, 1024, dump)) { >> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") && >> strstr(buffer, "ipv4")) { >> ? ? ? ? ? ? output->ac++; >> ? ? ? ? } >> ? ? } >> ? ? output->available = calloc(output->ac, sizeof(struct routes)); >> ? ? if(!output->available) >> ? ? ? ? return -1; >> ? ? struct routes *avail = output->available; >> ? ? rewind(dump); >> ? ? while(fgets(buffer, 1024, dump)) { >> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") && >> strstr(buffer, "ipv4")) { >> ? ? ? ? ? ? delim = strtok(buffer, "|"); >> ? ? ? ? ? ? for(int i = 0; i < 3; i++) >> ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); >> ? ? ? ? ? ? inet_pton(AF_INET, delim, &avail[output->ac].network); >> ? ? ? ? ? ? avail[output->ac].network = >> __builtin_bswap32(avail[output->ac].network); >> ? ? ? ? ? ? delim = strtok(NULL, "|"); >> ? ? ? ? ? ? unsigned int addr_count = atoi(delim); >> ? ? ? ? ? ? output->total_avail += addr_count; >> ? ? ? ? ? ? avail[output->ac].broadcast = >> avail[output->ac].network+(addr_count-1); >> ? ? ? ? ? ? avail[output->ac].mask = ~__builtin_bswap32((unsigned >> int)addr_count-1); >> ? ? ? ? ? ? output->ac++; >> ? ? ? ? } >> ? ? } >> ? ? fclose(dump); >> ? ? return 0; >> } >> >> int parse_dfz(char *dfz_dump, struct audit *output) { >> ? ? FILE *dump = fopen(dfz_dump, "r"); >> ? ? char buffer[1024] = {0}; >> ? ? int rc = 0, mult = 0, cidr = 0; >> ? ? char *delim; >> ? ? if(!dump) { >> ? ? ? ? return -1; >> ? ? } >> ? ? while(fgets(buffer, 1024, dump)) { >> ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9' && strtok(buffer, >> "/") && strchr(buffer, '.')) { >> ? ? ? ? ? ? rc++; >> ? ? ? ? } >> ? ? } >> ? ? output->dfz = calloc(rc, sizeof(struct routes)); >> ? ? output->dfz_count = rc; >> ? ? if(!output->dfz) { >> ? ? ? ? return -1; >> ? ? } >> ? ? rewind(dump); >> ? ? rc = 0; >> ? ? while(fgets(buffer, 1024, dump)) { >> ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9') { >> ? ? ? ? ? ? cidr = 0; >> ? ? ? ? ? ? delim = strtok(buffer, "/"); >> ? ? ? ? ? ? delim = strtok(NULL, "/"); >> ? ? ? ? ? ? if(!delim) { >> ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); >> ? ? ? ? ? ? ? ? continue; >> ? ? ? ? ? ? } >> ? ? ? ? ? ? mult = 1; >> ? ? ? ? ? ? for(int i = 0; i < 3; i++) { >> ? ? ? ? ? ? ? ? if(delim[i] >= '0' && delim[i] <= '9') { >> ? ? ? ? ? ? ? ? ? ? cidr = cidr * mult+(9-('9'-delim[i])); >> ? ? ? ? ? ? ? ? ? ? mult*=10; >> ? ? ? ? ? ? ? ? } >> ? ? ? ? ? ? } >> ? ? ? ? ? ? delim = strchr(buffer, '.'); >> ? ? ? ? ? ? if(!delim) { >> ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); >> ? ? ? ? ? ? ? ? continue; >> ? ? ? ? ? ? } >> ? ? ? ? ? ? output->dfz[rc].cidr = cidr; >> ? ? ? ? ? ? inet_pton(AF_INET, buffer, &output->dfz[rc].network); >> ? ? ? ? ? ? output->dfz[rc].cidr = cidr; >> ? ? ? ? ? ? output->dfz[rc].network = __builtin_bswap32((unsigned >> int)output->dfz[rc].network); >> ? ? ? ? ? ? output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); >> ? ? ? ? ? ? output->dfz[rc].broadcast = output->dfz[rc].network + >> ((~(unsigned int)0) >> cidr); >> ? ? ? ? ? ? output->dfz[rc].network = __builtin_bswap32((unsigned >> int)output->dfz[rc].network); >> ? ? ? ? ? ? output->dfz[rc].broadcast = >> __builtin_bswap32((unsigned int)output->dfz[rc].broadcast); >> ? ? ? ? ? ? rc++; >> ? ? ? ? ? ? memset(buffer, 0, 1024); >> ? ? ? ? } >> ? ? } >> ? ? fclose(dump); >> ? ? return 0; >> } >> >> int audit_reserved(struct audit *data) { >> ? ? int hijack_count = 0; >> ? ? for(int i = 0; i < data->dfz_count; i++) { >> ? ? ? ? unsigned int dfz_net = __builtin_bswap32((unsigned >> int)data->dfz[i].network); >> ? ? ? ? unsigned int dfz_bcast = __builtin_bswap32((unsigned >> int)data->dfz[i].broadcast); >> ? ? ? ? for(int r = 0; r < data->rc; r++) { >> ? ? ? ? ? ? unsigned int resv_net = __builtin_bswap32((unsigned >> int)data->reserved[r].network); >> ? ? ? ? ? ? unsigned int resv_bcast = __builtin_bswap32((unsigned >> int)data->reserved[r].broadcast); >> ? ? ? ? ? ? if(dfz_net >= resv_net && dfz_net <= resv_bcast) { >> ? ? ? ? ? ? ? ? hijack_count += ((dfz_bcast-dfz_net)+1); >> ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; >> ? ? ? ? ? ? ? ? char resv_network[INET_ADDRSTRLEN] = {0}; >> ? ? ? ? ? ? ? ? char resv_broadcast[INET_ADDRSTRLEN] = {0}; >> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, >> dfz_route, INET_ADDRSTRLEN); >> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->reserved[r].network, >> resv_network, INET_ADDRSTRLEN); >> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->reserved[r].broadcast, >> resv_broadcast, INET_ADDRSTRLEN); >> ? ? ? ? ? ? ? ? printf("%s/%d fell between reserved range %s -> >> %s [Adding %d addresses to potential hijack]\n", >> ? ? ? ? ? ? ? ? ? ? ? ?dfz_route, data->dfz[i].cidr, >> resv_network, resv_broadcast, (dfz_bcast-dfz_net)+1); >> ? ? ? ? ? ? } >> ? ? ? ? } >> ? ? ? ? for(int a = 0; a < data->ac; a++) { >> ? ? ? ? ? ? unsigned int avail_net = __builtin_bswap32((unsigned >> int)data->available[a].network); >> ? ? ? ? ? ? unsigned int avail_bcast = >> __builtin_bswap32((unsigned int)data->available[a].broadcast); >> ? ? ? ? ? ? if(dfz_net >= data->available[a].network && dfz_net >> <= data->available[a].broadcast) { >> ? ? ? ? ? ? ? ? hijack_count += >> ((data->available[a].broadcast-data->available[a].network)+1); >> ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; >> ? ? ? ? ? ? ? ? char avail_network[INET_ADDRSTRLEN] = {0}; >> ? ? ? ? ? ? ? ? char avail_broadcast[INET_ADDRSTRLEN] = {0}; >> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, >> dfz_route, INET_ADDRSTRLEN); >> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_net, avail_network, >> INET_ADDRSTRLEN); >> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_bcast, avail_broadcast, >> INET_ADDRSTRLEN); >> ? ? ? ? ? ? ? ? printf("%s/%d fell between available range %s -> >> %s\n", dfz_route, data->dfz[i].cidr, avail_network, avail_broadcast); >> ? ? ? ? ? ? } >> ? ? ? ? } >> ? ? } >> ? ? printf("Found %d potentially hijacked addresses\n", >> hijack_count); >> ? ? return 0; >> } >> >> int main(int argc, const char * argv[]) { >> ? ? struct audit data = {0}; >> ? ? if(parse_dfz(BGP_DUMP, &data)) >> ? ? ? ? return EXIT_FAILURE; >> ? ? if(parse_afrinic_extended(AFRINIC_EXT, &data)) >> ? ? ? ? return EXIT_FAILURE; >> ? ? printf("Found %d total available addresses and %d total >> reserved addresses\n", data.total_avail, data.total_resv); >> ? ? audit_reserved(&data); >> ? ? return EXIT_SUCCESS; >> } >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From madomey at hotmail.com Wed Oct 15 16:04:00 2025 From: madomey at hotmail.com (Marcus K. G. Adomey) Date: Wed, 15 Oct 2025 16:04:00 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: <44830741-6C2C-44D5-BBBA-369ACCF19838@yahoo.fr> References: <5DF5ED45-A4B2-4DEB-B279-A7C045495500@wacren.net> <44830741-6C2C-44D5-BBBA-369ACCF19838@yahoo.fr> Message-ID: Dear PDWG Members, REFLECTION AND RENEWAL IN THE PDWG The PDWG is central to AfriNIC?s PDP, yet its effectiveness has declined due to breakdown in constructive dialogue. As we move forward, we must reflect on what went wrong ? both in our processes and group dynamics ? and how we can rebuild a respectful, inclusive, and professional environment fit for building consensus on policies. Unfortunately, current discussions remain superficial, failing to address the root causes of the breakdown. This approach leaves deeper wounds untreated and risks repeating past mistakes. Let us commit to genuine reflection and impartial review, so we can transform the PDWG into a resilient, transparent, and collaborative platform it was meant to be. Warm regards, Marcus ________________________________ From: Gr?goire EHOUMI via RPD Sent: Tuesday, October 14, 2025 1:46 PM To: Oaiya Omo Cc: rpd Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual Hello, On Oct 12, 2025, at 6:31?AM, Omo Oaiya via RPD wrote: ? It?s great to see discussion back on the list, a good sign that the community spirit is still strong. I agree with Owen. What really matters is that the feedback loop stays open, clear, and timely. On Ben?s point, participation will grow if we make the PDP more inclusive and relevant. We should bring in people from IXPs, NRENs, academia, civil society, and sectors shaping Africa?s digital economy. Linking policy work to that wider digital transformation agenda will draw new energy and perspectives. Let?s keep it going. Best, Omo ?More inclusive? by offering a pleasant, productive PDP to the expected standards, right ? Policy discussions and meetings have always been open to anyone to join and participate. No one has been prevented from participating in pdp, except perhaps our behaviours may have discouraged, scared away many people in our diverse and fragile ecosystem. The board made a key prerequisite to resumption of PDP as below: "A key prerequisite will be to ensure that all community mailing lists maintain an atmosphere of civility and constructive engagement." Governments are more attentive now, watching and assessing us. It shouldn't be like before thanks for our collective efforts. ?More relevant? yes towards policy making for Number resources management, but without turning the PDP into an IG forum? Community, members, board and staff should make sure that policies we discuss and approve serve the interests AFRICA and not private, personal interests. Cheers, - Gr?goire -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Wed Oct 15 17:11:54 2025 From: sami.salih at outlook.com (Sami Salih) Date: Wed, 15 Oct 2025 17:11:54 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <3C3C3E6F-48C4-488D-8937-3E566E8ED9FB@delong.com> References: <3C3C3E6F-48C4-488D-8937-3E566E8ED9FB@delong.com> Message-ID: In such a complex situation, there are certainly more possibilities than the two you?ve outlined. Moving forward, I believe we can build a constructive dialogue if we agree on a few key principles: 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. 2. It?s essential to use available resources wisely, neither reserving large unused blocks nor rushing to exhaust them is a sustainable strategy. 3. The current statistics already reveal some noticeable imbalances, which suggests we shouldn?t continue in the same direction without adjustment. For me, I believe, we don?t yet have a real good need to free the reserved block, but I?m open to discussing any policy proposal that presents a genuine use case to utilize a logical portion of it. And to be clear, the staff are doing an excellent job within the framework provided, howver the discussion here is about broader structural issues, not their performance. Sent from Outlook for Android ________________________________ From: Owen DeLong Sent: Wednesday, October 15, 2025 11:58:12 AM To: Sami Salih Cc: jordi.palet at consulintel.es ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Either staff is approving fraudulent requests (in which case not such a great job) or they are not (in which case the existing statistics and concern about them is a poor predictor of future allocations). You can?t have it both ways. Owen On Oct 14, 2025, at 23:31, Sami Salih wrote: ? It?s not about the staff ? they are doing an excellent job, indeed. The issue lies in the broader structural situation in many of our countries. Looking at the statistics shared in yhis list earlier, it becomes obvious that what is labelled as the ?top 10? are not in fact the top African businesses when it comes to using v$ resources. Sent from Outlook for Android ________________________________ From: Owen DeLong Sent: Wednesday, October 15, 2025 8:39:00 AM To: Sami Salih Cc: jordi.palet at consulintel.es ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate That assumes a great many facts not in evidence and basically accuses every current applicant of fraud. It also calls into question the quality of the job done by the AFRINIC staff. If that?s truly an issue at the moment, then we should address the staff problems and correct those issues, but assuming that every applicant is a fraud is NOT a valid basis for policy. Owe On Oct 14, 2025, at 22:20, Sami Salih wrote: ? No, Owen If we can ensure that " present needs are actual" we wouldn't be having this debate. The moment unnecessary IPv4 space is assigned to a business, they will quickly monetize it through resource transfers. ________________________________ From: Owen DeLong Sent: Wednesday, October 15, 2025 3:34:38 am To: Sami Salih Cc: jordi.palet at consulintel.es ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate Remember, whatever you put on hold to protect future generations from significant scarcity subjects current generations to equivalent scarcity. The difference is that the future need is theoretical and the present needs are actual. Owen On Oct 14, 2025, at 15:39, Sami Salih wrote: ? That said, relying on African governments may be reasonable for countries with stable economic and political conditions. However, given the conflicts and instability present in several regions across the continent, it's wise to preserve sufficient resources for future generations, who may otherwise face significant scarcity. On a related note, the reserved IP blocks come at no cost. They don?t require active maintenance or storage infrastructure, just basic protection against misuse or hijacking. These reserves can be kept indefinitely. And once IPv6 becomes the dominant protocol, we can simply "let them go!". But for now, we need to keep our resources. Sami Salih, Sent from Outlook for Android ________________________________ From: jordi.palet--- via RPD Sent: Tuesday, October 14, 2025 7:06:14 PM To: RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate I would agree with you if all the economies have the same resources (not just economical ones, but also human resources, expertise, etc.), but we know is not the case. Now a different history is if any ISP in 1-2 years from now, has not *at least* started their deployment plans. In such a situation, I think it is a clear matter of governments, in their duty to protect citizens, taking strong actions against any service provider or industry not doing so. Of course that means the government networks itself need to use IPv6: they need to set the example, otherwise you can?t enforce it. Today deploying a *new* network using 464XLAT is even cheaper and easier than doing so with IPv4 or dual-stack. So this must be clearly enforced to obtain new licenses, as there is no excuse. This is valid for either cellular networks, broadband networks or even for enterprise networks using IPv6-mostly. I fully understand that is not the same for an existing network, that?s why they should have some more time, but at least have *clearly structured* plans, not just ?yes we are thinking on that? ... Saludos, Jordi @jordipalet El 14 oct 2025, a las 17:14, Owen DeLong escribi?: If it isn?t already deployed, I question this at this point. How long should the rest of the internet subsidize failure to deploy? Personally, I think we are past that point. Owen On Oct 14, 2025, at 02:05, jordi.palet--- via RPD wrote: ?Agree, however, we know very well that a small IPv4 pool (may be a /24 for each BGP PoP), is needed for interconnection with IPv4 Internet, as there may be still some old apps that require it. Regards, Jordi @jordipalet El 14 oct 2025, a las 10:46, Owen DeLong via RPD escribi?: Yes, exactly. The continuing presence of an IPv4 free pool at AFRINIC and the efforts to keep it from running out are actually counterproductive to progress in the African digital economy. Owen On Oct 14, 2025, at 01:22, Hendrik Visage wrote: ? Question: Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" --- Hendrik Visage Instant messaging: https://t.me/hvisage On 13 Oct 2025, at 16:43, Andrew Alston wrote: Hi All, I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. Thanks Andrew _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Wed Oct 15 18:41:15 2025 From: ben.roberts at afrinic.net (Ben Roberts - AfriNIC) Date: Wed, 15 Oct 2025 21:41:15 +0300 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: Message-ID: <1A569F83-1E16-46ED-949C-20D0C2E6F521@afrinic.net> 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. ++1 Sent from my iPhone > On 15 Oct 2025, at 20:13, Sami Salih wrote: > > > 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Thu Oct 16 03:19:17 2025 From: owen at delong.com (Owen DeLong) Date: Wed, 15 Oct 2025 20:19:17 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: References: <3C3C3E6F-48C4-488D-8937-3E566E8ED9FB@delong.com> Message-ID: <7DF23C6C-9BA4-4D58-BD12-341EE492A0F4@delong.com> > On Oct 15, 2025, at 10:11, Sami Salih wrote: > > In such a complex situation, there are certainly more possibilities than the two you?ve outlined. > > Moving forward, I believe we can build a constructive dialogue if we agree on a few key principles: > > 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. Less so than most perceive it to be, but yes, to some extent. > 2. It?s essential to use available resources wisely, neither reserving large unused blocks nor rushing to exhaust them is a sustainable strategy. The first part, I completely agree with. As to exhaustion, I?d have a great deal of difficulty calling exhausting IPv4 in AFRINIC tomorrow a ?rush? at this point. Global IPv4 RIR exhaustion in the other 4 RIRs (note this is not just the global north, all 4, at least two of which have significant populations south of the equator) exhaustion occurred several years ago. > 3. The current statistics already reveal some noticeable imbalances, which suggests we shouldn?t continue in the same direction without adjustment. I guess that depends on what you consider balanced and to what extent you think that resource allocations for IPv4 addresses should be balanced. I will note that if you go to the store on a day when they have a limited supply of $X, the first people to get there can generally buy $X and those who show up late generally cannot. Most people don?t call this unfair, they just call it ?The early bird gets the worm.? I?m not saying there should or should not be changes in how resource allocations within the AFRINIC service region are balanced, I have no dog in that particular fight. I am, however, saying that from a global perspective and for AFRINIC in particular, the continuing existence of the IPv4 tree pool is problematic in a number of ways and the longer it sits there, the more of an incentive it will create for fraud, mismanagement, graft, and corruption. > For me, I believe, we don?t yet have a real good need to free the reserved block, but I?m open to discussing any policy proposal that presents a genuine use case to utilize a logical portion of it. See above. The use case is the same as prior legitimate allocations under policy as it existed before global exhaustion. > And to be clear, the staff are doing an excellent job within the framework provided, howver the discussion here is about broader structural issues, not their performance. I think it?s a bit of both. There is definitely a history of staff issuing resources that should not have been issued even under the framework as it existed. I do not know to what extent this conduct has continued or not and I?m not making any accusations. I am merely stating historic fact here. Certainly some of the staff that remains in registration services are among those who knew or should have known that the fraud was occurring right under their noses and failed to take any effective action at the time. Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Thu Oct 16 03:35:10 2025 From: owen at delong.com (Owen DeLong) Date: Wed, 15 Oct 2025 20:35:10 -0700 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <5DF5ED45-A4B2-4DEB-B279-A7C045495500@wacren.net> <44830741-6C2C-44D5-BBBA-369ACCF19838@yahoo.fr> Message-ID: This strikes me as a very superficial comment on that? Please, elaborate on what you view as the true root causes of the breakdown and the deeper wounds? If you want everyone else to commit to genuine reflection and impartial review, how about starting yourself? Owen > On Oct 15, 2025, at 09:04, Marcus K. G. Adomey wrote: > > Dear PDWG Members, > > REFLECTION AND RENEWAL IN THE PDWG > > The PDWG is central to AfriNIC?s PDP, yet its effectiveness has declined due to breakdown in constructive dialogue. As we move forward, we must reflect on what went wrong ? both in our processes and group dynamics ? and how we can rebuild a respectful, inclusive, and professional environment fit for building consensus on policies. > > Unfortunately, current discussions remain superficial, failing to address the root causes of the breakdown. This approach leaves deeper wounds untreated and risks repeating past mistakes. > > Let us commit to genuine reflection and impartial review, so we can transform the PDWG into a resilient, transparent, and collaborative platform it was meant to be. > > Warm regards, > > > Marcus > From: Gr?goire EHOUMI via RPD > Sent: Tuesday, October 14, 2025 1:46 PM > To: Oaiya Omo > Cc: rpd > Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual > > Hello, > >> On Oct 12, 2025, at 6:31?AM, Omo Oaiya via RPD wrote: >> >> ? >> It?s great to see discussion back on the list, a good sign that the community spirit is still strong. I agree with Owen. What really matters is that the feedback loop stays open, clear, and timely. >> On Ben?s point, participation will grow if we make the PDP more inclusive and relevant. We should bring in people from IXPs, NRENs, academia, civil society, and sectors shaping Africa?s digital economy. Linking policy work to that wider digital transformation agenda will draw new energy and perspectives. >> Let?s keep it going. >> Best, >> Omo > ?More inclusive? by offering a pleasant, productive PDP to the expected standards, right ? > > Policy discussions and meetings have always been open to anyone to join and participate. No one has been prevented from participating in pdp, except perhaps our behaviours may have discouraged, scared away many people in our diverse and fragile ecosystem. > > The board made a key prerequisite to resumption of PDP as below: > "A key prerequisite will be to ensure that all community mailing lists maintain an atmosphere of civility and constructive engagement." > > Governments are more attentive now, watching and assessing us. > It shouldn't be like before thanks for our collective efforts. > > ?More relevant? yes towards policy making for Number resources management, but without turning the PDP into an IG forum? Community, members, board and staff should make sure that policies we discuss and approve serve the interests AFRICA and not private, personal interests. > > Cheers, > - > Gr?goire > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Thu Oct 16 03:38:51 2025 From: owen at delong.com (Owen DeLong) Date: Wed, 15 Oct 2025 20:38:51 -0700 Subject: [rpd] Questions about IP Allocation rate In-Reply-To: <026901dc3dc1$bbed8440$33c88cc0$@afrinic.net> References: <8EA222C4-FAA9-4228-8E54-6CC98830D271@delong.com> <026901dc3dc1$bbed8440$33c88cc0$@afrinic.net> Message-ID: <27945937-B934-4C61-AE19-350D2848F7A4@delong.com> I?m not convinced that the rest of the world should wait for them to catch up. You pose it as a situation where they would be held up by lack of IPv4 resources. I pose it as a situation where the rest of Africa is being held up waiting for them to make use of those resources as they are denied to the rest of Africa. I guess it?s a matter of perspective. Owen > On Oct 15, 2025, at 03:51, ben.roberts at afrinic.net wrote: > > Owen, > South Africa has approx 850 AS Numbers with approx 64 million population which is 0.00001328125 members per capita of population. > > The whole of Africa has population of say 1.5 Billion. If the continental average were to catch up with South Africa, arguably the most digitally advanced African Nation then one can apply that average x the pan African population to get > > 0.00001328125 x 1.5 Billion = 19,921 members > > So an increase from 2400 number holding resource members to 19,921, so yes exactly about 17,000 extra members are possible. Each one holding AS number, a nominal IPv4 range, plus a bigger IPv6 range. > > While some African nations are up to 15 to 20 years behind South Africa in terms of digital development, they should not be held back in catch up by availability of IP resources don?t you think? > > Regards > > Ben > > From: Owen DeLong via RPD > Sent: 15 October 2025 11:55 > To: Noah > Cc: RPD > Subject: Re: [rpd] Questions about IP Allocation rate > > Do you really expect 17,000+ legitimate new entrants in the next X years (where X is the number of years you expect before catering to laggards is no longer a requirement) in the AFRINIC service area? I think that?s a pretty gross overestimate. > > Owen > > > >> On Oct 15, 2025, at 00:39, Noah > wrote: >> >> ? >> >> >> >> On Wed, 15 Oct 2025, 9:42?am jordi.palet--- via RPD, > wrote: >>> Is not for the peering (it is not needed even for IXPs, we can use IPv6-only), is for the NAT64. >> >> >> RFC6146 is widely supported by most vendors today and a bare minimum of /24 v4 space for translators is foresight grounded on reality of v4/v6 co-existance. >> >> More so for new entrants who must not be succummed to IPv$ brokers/leasers who stockpile to monetize in future based on scarcity. >> >> Noah >> >> Noah >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From sami.salih at outlook.com Thu Oct 16 06:35:55 2025 From: sami.salih at outlook.com (Sami Salih) Date: Thu, 16 Oct 2025 06:35:55 +0000 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <7DF23C6C-9BA4-4D58-BD12-341EE492A0F4@delong.com> References: <3C3C3E6F-48C4-488D-8937-3E566E8ED9FB@delong.com> <7DF23C6C-9BA4-4D58-BD12-341EE492A0F4@delong.com> Message-ID: No comment from my side regarding the staff issue ? such things happen everywhere. What really matters is how we deal with these situations. On another note, don?t forget: the early worm gets eaten. So, be the bird if you must be early ? not the worm. ? Sami Salih. ________________________________ From: Owen DeLong Sent: Thursday, October 16, 2025 6:19:58 am To: Sami Salih Cc: jordi.palet at consulintel.es ; RPD Subject: Re: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate On Oct 15, 2025, at 10:11, Sami Salih wrote: In such a complex situation, there are certainly more possibilities than the two you?ve outlined. Moving forward, I believe we can build a constructive dialogue if we agree on a few key principles: 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. Less so than most perceive it to be, but yes, to some extent. 2. It?s essential to use available resources wisely, neither reserving large unused blocks nor rushing to exhaust them is a sustainable strategy. The first part, I completely agree with. As to exhaustion, I?d have a great deal of difficulty calling exhausting IPv4 in AFRINIC tomorrow a ?rush? at this point. Global IPv4 RIR exhaustion in the other 4 RIRs (note this is not just the global north, all 4, at least two of which have significant populations south of the equator) exhaustion occurred several years ago. 3. The current statistics already reveal some noticeable imbalances, which suggests we shouldn?t continue in the same direction without adjustment. I guess that depends on what you consider balanced and to what extent you think that resource allocations for IPv4 addresses should be balanced. I will note that if you go to the store on a day when they have a limited supply of $X, the first people to get there can generally buy $X and those who show up late generally cannot. Most people don?t call this unfair, they just call it ?The early bird gets the worm.? I?m not saying there should or should not be changes in how resource allocations within the AFRINIC service region are balanced, I have no dog in that particular fight. I am, however, saying that from a global perspective and for AFRINIC in particular, the continuing existence of the IPv4 tree pool is problematic in a number of ways and the longer it sits there, the more of an incentive it will create for fraud, mismanagement, graft, and corruption. For me, I believe, we don?t yet have a real good need to free the reserved block, but I?m open to discussing any policy proposal that presents a genuine use case to utilize a logical portion of it. See above. The use case is the same as prior legitimate allocations under policy as it existed before global exhaustion. And to be clear, the staff are doing an excellent job within the framework provided, howver the discussion here is about broader structural issues, not their performance. I think it?s a bit of both. There is definitely a history of staff issuing resources that should not have been issued even under the framework as it existed. I do not know to what extent this conduct has continued or not and I?m not making any accusations. I am merely stating historic fact here. Certainly some of the staff that remains in registration services are among those who knew or should have known that the fraud was occurring right under their noses and failed to take any effective action at the time. Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Thu Oct 16 07:01:55 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Thu, 16 Oct 2025 09:01:55 +0200 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: <34cba83c-e08f-48d5-9815-ee9637e618ba@gmail.com> References: <34cba83c-e08f-48d5-9815-ee9637e618ba@gmail.com> Message-ID: <2cd1aca8-6c68-4ed0-8eb9-18835cf989a3@uls.co.za> Hi, Two notes from my side: 1.? Isn't this (in part) what the whole AS0 policy was about? Such that space that's reserved/not issued by Afrinic can be protected?? (Having inherited previously abused space ... I'm 100% behind such a policy). 2.? Whilst I agree with Andrew that it's difficult to determine the exact Geographical location of originations, and I like his concept of looking at reserved/available ASNs, I do think something that makes an equal amount of sense is to get an idea of the space issued to an org not originated by that org ... there are legitimate cases (eg, we originate space on behalf of one of our customers, used exclusively by that client), so I'm more interested in cases like "space issued to org X originated from Y non-X ASNs" (ie, don't count space where both the ASN and the space is assigned to the same ORG).? As concrete examples: 154.73.32.0/22 => org: ORG-ULSC1-AFRINIC AS327767 => org: ORG-ULSC1-AFRINIC That need not be counted. 102.214.182.0/23 => 102.214.180.0/22 => org: ORG-DCC1-AFRINIC AS327767 => org: ORG-ULSC1-AFRINIC Count these cases, and group by ORG.? So the above would result in: ORG-DCC1-AFRINIC originates 1 prefix from 1 alternative ASN. Andrew - I'd be happy to assist with some code for counting this if you throw the base on github and don't mind making that dump of yours for the DFZ data available. Kind regards, Jaco On 2025/10/15 14:35, Fernando Frediani wrote: > > Yeah it could be, but I would say that alone is already something that > can bring attention to resources because it is not what is widely > expected. I would easily believe that a fair amount of space announce > by other ASNs other than the one linked to it in the whois may not be > what was desired or justified at the same resources were allocated. > There are valid examples as you mentioned, but I would say they are > the fewer. > > I think the most important in this context is find out if the > resources are being use in Africa or not which it is slightly more > complex to asses than matching with whois data. > > Fernando > > On 10/15/2025 9:24 AM, Andrew Alston wrote: >> Hi Fernando, >> >> It's unfortunately extremely difficult to do this - because while an >> ASN may be allocated by AfriNIC it could be announced from anywhere, >> and even in the case of where an ASN is allocated by RIPE, it may be >> used in Africa to announce AfriNIC space (Liquid Telecom is an >> example of this, where 30844 is a RIPE ASN but almost all the space >> under it is afrinic allocated and announced in Africa). >> >> It would be possible to extend the code I wrote to show the source >> ASN of the prefix's?that are reserved - and then potentially to match >> that against other AfriNIC data to show who the ASN is owned by (if >> the ASN itself is allocated, in my verification I found that many of >> these prefix's are being announced by ASN's that are marked as >> available or reserved) >> >> I will see what I can do about adding that extra code at some point >> when I find the time. >> >> Thanks >> >> Andrew >> >> >> On Wed, Oct 15, 2025 at 3:14?PM Fernando Frediani >> wrote: >> >> Would it be possible to get detailed information about AfriNic >> prefixes that are currently being announced by different ASNs >> they are linked to and potentially being used out of the Africa >> region as well ? That would be a pretty interesting information >> to see. >> >> Regards >> Fernando >> >> On 10/15/2025 8:40 AM, Andrew Alston wrote: >>> Hi Guys, >>> >>> So - Firstly a few notes on using the code I'm going to paste below. >>> >>> I created the BGP dump file on a juniper router by running a >>> "show route protocol bgp | save bgp.dump.txt" and then copying >>> that dump file to my local system from the Juniper router.? Note >>> - this produces a roughly 400meg file on a full table router and >>> it takes quite a while to run the command. >>> Then - I used the delegated-afrinic-extended-latest file >>> downloaded from the stats ftp server. >>> >>> In the code below - if you wish to run similar - change the char >>> BGP_DUMP[256] and char AFRINIC_EXT[256] global variables to >>> match the pathing to the relevant files. >>> >>> Note that there is some weirdness?in this code to deal with >>> endianness - and I will openly admit its not the cleanest (or >>> probably most efficient) code - but it does work and I've >>> verified the results. >>> >>> I've pasted the code below the results section. >>> >>> So - first the results: >>> >>> Found 824064 total available addresses and 4482304 total >>> reserved addresses >>> 41.57.124.0/22 fell between reserved >>> range 41.57.124.0 -> 41.57.127.255 [Adding 1024 addresses to >>> potential hijack] >>> 41.57.124.0/23 fell between reserved >>> range 41.57.124.0 -> 41.57.127.255 [Adding 512 addresses to >>> potential hijack] >>> 41.57.124.0/24 fell between reserved >>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>> potential hijack] >>> 41.57.125.0/24 fell between reserved >>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>> potential hijack] >>> 41.57.126.0/24 fell between reserved >>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>> potential hijack] >>> 41.57.127.0/24 fell between reserved >>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>> potential hijack] >>> 41.77.64.0/21 fell between reserved range >>> 41.77.64.0 -> 41.77.71.255 [Adding 2048 addresses to potential >>> hijack] >>> 41.138.192.0/24 fell between reserved >>> range 41.138.192.0 -> 41.138.223.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.224.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.225.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.226.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.227.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.228.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.229.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.230.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.231.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.232.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.233.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.234.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.235.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.236.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.237.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.238.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.239.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.240.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.241.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.242.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.243.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.244.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.245.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.246.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.247.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.248.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.249.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.250.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.251.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.254.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.204.255.0/24 fell between reserved >>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.205.224.0/19 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 8192 addresses to >>> potential hijack] >>> 41.205.225.0/24 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.205.232.0/24 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.205.234.0/24 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.205.235.0/24 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.205.237.0/24 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.205.238.0/24 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.205.239.0/24 fell between reserved >>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>> potential hijack] >>> 41.220.48.0/20 fell between reserved >>> range 41.220.48.0 -> 41.220.63.255 [Adding 4096 addresses to >>> potential hijack] >>> 80.88.6.0/24 fell between reserved range >>> 80.88.6.0 -> 80.88.6.255 [Adding 256 addresses to potential hijack] >>> 102.128.74.0/24 fell between reserved >>> range 102.128.72.0 -> 102.128.75.255 [Adding 256 addresses to >>> potential hijack] >>> 102.135.164.0/24 fell between reserved >>> range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to >>> potential hijack] >>> 102.135.165.0/24 fell between reserved >>> range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to >>> potential hijack] >>> 102.135.166.0/24 fell between reserved >>> range 102.135.164.0 -> 102.135.167.255 [Adding 256 addresses to >>> potential hijack] >>> 102.219.128.0/24 fell between reserved >>> range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to >>> potential hijack] >>> 102.219.129.0/24 fell between reserved >>> range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to >>> potential hijack] >>> 102.219.130.0/24 fell between reserved >>> range 102.219.128.0 -> 102.219.131.255 [Adding 256 addresses to >>> potential hijack] >>> 102.221.148.0/22 fell between reserved >>> range 102.221.144.0 -> 102.221.151.255 [Adding 1024 addresses to >>> potential hijack] >>> 156.0.254.0/24 fell between reserved >>> range 156.0.254.0 -> 156.0.254.255 [Adding 256 addresses to >>> potential hijack] >>> 160.119.208.0/24 fell between reserved >>> range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to >>> potential hijack] >>> 160.119.209.0/24 fell between reserved >>> range 160.119.208.0 -> 160.119.211.255 [Adding 256 addresses to >>> potential hijack] >>> 164.160.192.0/21 fell between reserved >>> range 164.160.192.0 -> 164.160.223.255 [Adding 2048 addresses to >>> potential hijack] >>> 169.255.164.0/22 fell between reserved >>> range 169.255.164.0 -> 169.255.167.255 [Adding 1024 addresses to >>> potential hijack] >>> 193.188.7.0/24 fell between reserved >>> range 193.188.7.0 -> 193.188.7.255 [Adding 256 addresses to >>> potential hijack] >>> 196.13.203.0/24 fell between reserved >>> range 196.13.203.0 -> 196.13.203.255 [Adding 256 addresses to >>> potential hijack] >>> 196.20.60.0/24 fell between reserved >>> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >>> potential hijack] >>> 196.20.61.0/24 fell between reserved >>> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >>> potential hijack] >>> 196.20.62.0/24 fell between reserved >>> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >>> potential hijack] >>> 196.41.74.0/24 fell between reserved >>> range 196.41.74.0 -> 196.41.74.255 [Adding 256 addresses to >>> potential hijack] >>> 196.43.252.0/24 fell between reserved >>> range 196.43.252.0 -> 196.43.252.255 [Adding 256 addresses to >>> potential hijack] >>> 196.46.18.0/24 fell between reserved >>> range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to >>> potential hijack] >>> 196.46.19.0/24 fell between reserved >>> range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to >>> potential hijack] >>> 196.46.152.0/24 fell between reserved >>> range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to >>> potential hijack] >>> 196.46.153.0/24 fell between reserved >>> range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to >>> potential hijack] >>> 196.46.154.0/23 fell between reserved >>> range 196.46.152.0 -> 196.46.159.255 [Adding 512 addresses to >>> potential hijack] >>> 196.50.21.0/24 fell between reserved >>> range 196.50.21.0 -> 196.50.21.255 [Adding 256 addresses to >>> potential hijack] >>> 196.53.113.0/24 fell between reserved >>> range 196.52.0.0 -> 196.55.255.255 [Adding 256 addresses to >>> potential hijack] >>> 196.54.72.0/23 fell between reserved >>> range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to >>> potential hijack] >>> 196.55.102.0/23 fell between reserved >>> range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to >>> potential hijack] >>> 196.63.243.0/24 fell between reserved >>> range 196.62.0.0 -> 196.63.255.255 [Adding 256 addresses to >>> potential hijack] >>> 196.195.4.0/24 fell between reserved >>> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >>> potential hijack] >>> 196.195.15.0/24 fell between reserved >>> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >>> potential hijack] >>> 196.195.253.0/24 fell between reserved >>> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >>> potential hijack] >>> 197.157.200.0/22 fell between reserved >>> range 197.157.200.0 -> 197.157.203.255 [Adding 1024 addresses to >>> potential hijack] >>> 197.231.248.0/22 fell between reserved >>> range 197.231.248.0 -> 197.231.251.255 [Adding 1024 addresses to >>> potential hijack] >>> 197.231.248.0/24 fell between reserved >>> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >>> potential hijack] >>> 197.231.249.0/24 fell between reserved >>> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >>> potential hijack] >>> 197.231.250.0/24 fell between reserved >>> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >>> potential hijack] >>> 197.231.251.0/24 fell between reserved >>> range 197.231.248.0 -> 197.231.251.255 [Adding 256 addresses to >>> potential hijack] >>> 197.234.208.0/24 fell between reserved >>> range 197.234.208.0 -> 197.234.215.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.224.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.225.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.226.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.227.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.229.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.231.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.232.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.233.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.234.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.235.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.236.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.237.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.238.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.239.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.240.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.241.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.242.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.243.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.244.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.245.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.246.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.247.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.248.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.249.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.250.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.251.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.252.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.254.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> 212.12.255.0/24 fell between reserved >>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>> potential hijack] >>> Found 50176 potentially hijacked addresses >>> >>> --- Below here is the code (I didn't know if I could send >>> attachments to the RPD list so I just pasted the code straight) --- >>> >>> // >>> // ?main.c >>> // ?AfrinicAudit >>> // >>> // ?Created by Andrew Alston on 15/10/2025. >>> // ?Code is considered open use with no restrictions. >>> // >>> >>> #include >>> #include >>> #include >>> #include >>> >>> char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; >>> char AFRINIC_EXT[256] = >>> "/Users/aalston/audit/delegated-afrinic-extended-latest"; >>> >>> struct routes { >>> ? ? unsigned int network; >>> ? ? unsigned int broadcast; >>> ? ? unsigned int mask; >>> ? ? unsigned short cidr; >>> }; >>> >>> struct audit { >>> ? ? struct routes *dfz; >>> ? ? int dfz_count; >>> ? ? struct routes *reserved; >>> ? ? int total_resv; >>> ? ? int rc; >>> ? ? struct routes *available; >>> ? ? int total_avail; >>> ? ? int ac; >>> }; >>> >>> int parse_afrinic_extended(char *afext, struct audit *output) { >>> ? ? FILE *dump = fopen(afext, "r"); >>> ? ? if(!dump) >>> ? ? ? ? return -1; >>> ? ? char buffer[1024] = {0}; >>> ? ? char *delim; >>> ? ? output->rc = 0; >>> ? ? while(fgets(buffer, 1024, dump)) { >>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && >>> strstr(buffer, "ipv4")) { >>> ? ? ? ? ? ? output->rc++; >>> ? ? ? ? } >>> ? ? } >>> ? ? output->reserved = calloc(output->rc, sizeof(struct routes)); >>> ? ? if(!output->reserved) >>> ? ? ? ? return -1; >>> ? ? output->rc = 0; >>> ? ? struct routes *resv = output->reserved; >>> ? ? rewind(dump); >>> ? ? while(fgets(buffer, 1024, dump)) { >>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") && >>> strstr(buffer, "ipv4")) { >>> ? ? ? ? ? ? delim = strtok(buffer, "|"); >>> ? ? ? ? ? ? for(int i = 0; i < 3; i++) >>> ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); >>> ? ? ? ? ? ? inet_pton(AF_INET, delim, &resv[output->rc].network); >>> ? ? ? ? ? ? resv[output->rc].network = >>> __builtin_bswap32(resv[output->rc].network); >>> ? ? ? ? ? ? delim = strtok(NULL, "|"); >>> ? ? ? ? ? ? unsigned int addr_count = atoi(delim); >>> ? ? ? ? ? ? output->total_resv += addr_count; >>> ? ? ? ? ? ? resv[output->rc].broadcast = >>> resv[output->rc].network+(addr_count-1); >>> ? ? ? ? ? ? resv[output->rc].network = >>> __builtin_bswap32(resv[output->rc].network); >>> ? ? ? ? ? ? resv[output->rc].broadcast = >>> __builtin_bswap32(resv[output->rc].broadcast); >>> ? ? ? ? ? ? resv[output->rc].mask = ~__builtin_bswap32((unsigned >>> int)addr_count-1); >>> ? ? ? ? ? ? output->rc++; >>> ? ? ? ? } >>> ? ? } >>> ? ? rewind(dump); >>> ? ? while(fgets(buffer, 1024, dump)) { >>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") >>> && strstr(buffer, "ipv4")) { >>> ? ? ? ? ? ? output->ac++; >>> ? ? ? ? } >>> ? ? } >>> ? ? output->available = calloc(output->ac, sizeof(struct routes)); >>> ? ? if(!output->available) >>> ? ? ? ? return -1; >>> ? ? struct routes *avail = output->available; >>> ? ? rewind(dump); >>> ? ? while(fgets(buffer, 1024, dump)) { >>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") >>> && strstr(buffer, "ipv4")) { >>> ? ? ? ? ? ? delim = strtok(buffer, "|"); >>> ? ? ? ? ? ? for(int i = 0; i < 3; i++) >>> ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); >>> ? ? ? ? ? ? inet_pton(AF_INET, delim, &avail[output->ac].network); >>> ? ? ? ? ? ? avail[output->ac].network = >>> __builtin_bswap32(avail[output->ac].network); >>> ? ? ? ? ? ? delim = strtok(NULL, "|"); >>> ? ? ? ? ? ? unsigned int addr_count = atoi(delim); >>> ? ? ? ? ? ? output->total_avail += addr_count; >>> ? ? ? ? ? ? avail[output->ac].broadcast = >>> avail[output->ac].network+(addr_count-1); >>> ? ? ? ? ? ? avail[output->ac].mask = >>> ~__builtin_bswap32((unsigned int)addr_count-1); >>> ? ? ? ? ? ? output->ac++; >>> ? ? ? ? } >>> ? ? } >>> ? ? fclose(dump); >>> ? ? return 0; >>> } >>> >>> int parse_dfz(char *dfz_dump, struct audit *output) { >>> ? ? FILE *dump = fopen(dfz_dump, "r"); >>> ? ? char buffer[1024] = {0}; >>> ? ? int rc = 0, mult = 0, cidr = 0; >>> ? ? char *delim; >>> ? ? if(!dump) { >>> ? ? ? ? return -1; >>> ? ? } >>> ? ? while(fgets(buffer, 1024, dump)) { >>> ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9' && >>> strtok(buffer, "/") && strchr(buffer, '.')) { >>> ? ? ? ? ? ? rc++; >>> ? ? ? ? } >>> ? ? } >>> ? ? output->dfz = calloc(rc, sizeof(struct routes)); >>> ? ? output->dfz_count = rc; >>> ? ? if(!output->dfz) { >>> ? ? ? ? return -1; >>> ? ? } >>> ? ? rewind(dump); >>> ? ? rc = 0; >>> ? ? while(fgets(buffer, 1024, dump)) { >>> ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9') { >>> ? ? ? ? ? ? cidr = 0; >>> ? ? ? ? ? ? delim = strtok(buffer, "/"); >>> ? ? ? ? ? ? delim = strtok(NULL, "/"); >>> ? ? ? ? ? ? if(!delim) { >>> ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); >>> ? ? ? ? ? ? ? ? continue; >>> ? ? ? ? ? ? } >>> ? ? ? ? ? ? mult = 1; >>> ? ? ? ? ? ? for(int i = 0; i < 3; i++) { >>> ? ? ? ? ? ? ? ? if(delim[i] >= '0' && delim[i] <= '9') { >>> ? ? ? ? ? ? ? ? ? ? cidr = cidr * mult+(9-('9'-delim[i])); >>> ? ? ? ? ? ? ? ? ? ? mult*=10; >>> ? ? ? ? ? ? ? ? } >>> ? ? ? ? ? ? } >>> ? ? ? ? ? ? delim = strchr(buffer, '.'); >>> ? ? ? ? ? ? if(!delim) { >>> ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); >>> ? ? ? ? ? ? ? ? continue; >>> ? ? ? ? ? ? } >>> ? ? ? ? ? ? output->dfz[rc].cidr = cidr; >>> ? ? ? ? ? ? inet_pton(AF_INET, buffer, &output->dfz[rc].network); >>> ? ? ? ? ? ? output->dfz[rc].cidr = cidr; >>> ? ? ? ? ? ? output->dfz[rc].network = >>> __builtin_bswap32((unsigned int)output->dfz[rc].network); >>> ? ? ? ? ? ? output->dfz[rc].mask = (~(unsigned int)0) << (32-cidr); >>> ? ? ? ? ? ? output->dfz[rc].broadcast = output->dfz[rc].network >>> + ((~(unsigned int)0) >> cidr); >>> ? ? ? ? ? ? output->dfz[rc].network = >>> __builtin_bswap32((unsigned int)output->dfz[rc].network); >>> ? ? ? ? ? ? output->dfz[rc].broadcast = >>> __builtin_bswap32((unsigned int)output->dfz[rc].broadcast); >>> ? ? ? ? ? ? rc++; >>> ? ? ? ? ? ? memset(buffer, 0, 1024); >>> ? ? ? ? } >>> ? ? } >>> ? ? fclose(dump); >>> ? ? return 0; >>> } >>> >>> int audit_reserved(struct audit *data) { >>> ? ? int hijack_count = 0; >>> ? ? for(int i = 0; i < data->dfz_count; i++) { >>> ? ? ? ? unsigned int dfz_net = __builtin_bswap32((unsigned >>> int)data->dfz[i].network); >>> ? ? ? ? unsigned int dfz_bcast = __builtin_bswap32((unsigned >>> int)data->dfz[i].broadcast); >>> ? ? ? ? for(int r = 0; r < data->rc; r++) { >>> ? ? ? ? ? ? unsigned int resv_net = __builtin_bswap32((unsigned >>> int)data->reserved[r].network); >>> ? ? ? ? ? ? unsigned int resv_bcast = >>> __builtin_bswap32((unsigned int)data->reserved[r].broadcast); >>> ? ? ? ? ? ? if(dfz_net >= resv_net && dfz_net <= resv_bcast) { >>> ? ? ? ? ? ? ? ? hijack_count += ((dfz_bcast-dfz_net)+1); >>> ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; >>> ? ? ? ? ? ? ? ? char resv_network[INET_ADDRSTRLEN] = {0}; >>> ? ? ? ? ? ? ? ? char resv_broadcast[INET_ADDRSTRLEN] = {0}; >>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, >>> dfz_route, INET_ADDRSTRLEN); >>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->reserved[r].network, >>> resv_network, INET_ADDRSTRLEN); >>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->reserved[r].broadcast, >>> resv_broadcast, INET_ADDRSTRLEN); >>> ? ? ? ? ? ? ? ? printf("%s/%d fell between reserved range %s -> >>> %s [Adding %d addresses to potential hijack]\n", >>> ? ? ? ? ? ? ? ? ? ? ? ?dfz_route, data->dfz[i].cidr, >>> resv_network, resv_broadcast, (dfz_bcast-dfz_net)+1); >>> ? ? ? ? ? ? } >>> ? ? ? ? } >>> ? ? ? ? for(int a = 0; a < data->ac; a++) { >>> ? ? ? ? ? ? unsigned int avail_net = __builtin_bswap32((unsigned >>> int)data->available[a].network); >>> ? ? ? ? ? ? unsigned int avail_bcast = >>> __builtin_bswap32((unsigned int)data->available[a].broadcast); >>> ? ? ? ? ? ? if(dfz_net >= data->available[a].network && dfz_net >>> <= data->available[a].broadcast) { >>> ? ? ? ? ? ? ? ? hijack_count += >>> ((data->available[a].broadcast-data->available[a].network)+1); >>> ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; >>> ? ? ? ? ? ? ? ? char avail_network[INET_ADDRSTRLEN] = {0}; >>> ? ? ? ? ? ? ? ? char avail_broadcast[INET_ADDRSTRLEN] = {0}; >>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, >>> dfz_route, INET_ADDRSTRLEN); >>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_net, avail_network, >>> INET_ADDRSTRLEN); >>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_bcast, >>> avail_broadcast, INET_ADDRSTRLEN); >>> ? ? ? ? ? ? ? ? printf("%s/%d fell between available range %s -> >>> %s\n", dfz_route, data->dfz[i].cidr, avail_network, >>> avail_broadcast); >>> ? ? ? ? ? ? } >>> ? ? ? ? } >>> ? ? } >>> ? ? printf("Found %d potentially hijacked addresses\n", >>> hijack_count); >>> ? ? return 0; >>> } >>> >>> int main(int argc, const char * argv[]) { >>> ? ? struct audit data = {0}; >>> ? ? if(parse_dfz(BGP_DUMP, &data)) >>> ? ? ? ? return EXIT_FAILURE; >>> ? ? if(parse_afrinic_extended(AFRINIC_EXT, &data)) >>> ? ? ? ? return EXIT_FAILURE; >>> ? ? printf("Found %d total available addresses and %d total >>> reserved addresses\n", data.total_avail, data.total_resv); >>> ? ? audit_reserved(&data); >>> ? ? return EXIT_SUCCESS; >>> } >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Thu Oct 16 07:11:08 2025 From: owen at delong.com (Owen DeLong) Date: Thu, 16 Oct 2025 00:11:08 -0700 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: <2cd1aca8-6c68-4ed0-8eb9-18835cf989a3@uls.co.za> References: <2cd1aca8-6c68-4ed0-8eb9-18835cf989a3@uls.co.za> Message-ID: An HTML attachment was scrubbed... URL: From jaco at uls.co.za Thu Oct 16 07:33:11 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Thu, 16 Oct 2025 09:33:11 +0200 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> Message-ID: <069b88a9-0762-479d-84cf-de4eed64520c@uls.co.za> Hi Hendrik, I'm in two minds on this.? On the one hand ... let it burn seems good. On the other hand, the single largest cheap hosting provider is SA still has no sensible plan on deploying IPv6 as far as I can tell, neither does any of the MNOs. Given the hosting provider can fix their crap QUICKLY, and the larger problem there would be to get their CUSTOMERS (who's in my experience generally small(ish) scale wordpress deployers - most of them I don't want to call developers because configuring plugins shouldn't be considered development) to deploy AAAA records. The MNOs (at least two of them) claim they're ready, but no customer wants it ... and when the customers ask, they're being told it's in the roadmap but no timelines has been set since there's not high demand. Doing v6-only on hosting side, and then using a small amount of v4 space to stateless NAT into the v6 infra is easy.? There are rumours (good authority but I've not personally confirmed it) that Facebook does exactly this already, and given it's stateless I can imagine that. My concern is getting CG-NAT just right is non-trivial, as anybody that provides services even marginally more complex than http will attest to.? And given the above situation where hosting providers are reluctant to deploy IPv6 for some reason. INVARIABLY when we are for AAAA records for services run externally where we manage DNS, we're being told one of two things: 1.? There's not IPv6 available; or 2.? Nobody cares about IPv6 so we don't bother. This seems like circular reasoning to me, nobody cares because nobody has it, and nobody has it because nobody cares. IPv6 for me seems more and more like the answer to IPv$ (which I differentiate from IPv4 ...). Reality is that there is only one way IPv6 will become a reality, and that's by letting IPv4 burn down and causing it to break. Until customers can't get to stuff because no IPv6 nobody is going to care. The ONLY customers I've got asking for IPv6 are those with home cameras that streams ... typically using RTP of sorts, and here what ends up happening is that the camera suppliers are making boatloads of money thanks to IPv4 since that means they get to sell a platform, camera connects to platform, and streaming goes through platform (TURN protocol).? The performance is poor, and given most of these I've investigated sits in HK - that also raises some privacy concerns about who has access to video feeds. When those customers gets IPv6 I get two positives: 1.? Their streaming is more reliable (no NAT ... no need to TURN via HK, results in less jitter, less buffering, less freezing and skipping). 2.? Overall less bandwidth ... for some reason I haven't investigated yet. On the one hand I like having happy customers (need IPv4 or else they can't get to www.{somerandomsite}.co.za).? On the other hand, let it burn so we can stop having these discussions. Kind regards, Jaco On 2025/10/14 10:21, Hendrik Visage wrote: > Question: > > ?Shouldn?t we rather consider pushing IPv6 deployment assistance > across Africa? ie. let the rest of the IPv4 go ASAP without much > resistance instead of making this a begging/pleading/fighting game? > > ARIN (North America) & RIPE (Europe) serviced areas are way ahead of > IPv6 roll outs, ?cause they don?t have any left, and looking at > AfriNIC services countries, we are still have an abundance of IPv4, so > IPv6 percentage roll outs are very low, and rathe we should be pushing > to mirror the IPv6 percentage rollout and usage rather than fighting > over the few remaining IPv4s if we want to grow digital rollouts. > > Perhaps even moving to a state of: ?You can have IPv6, once you?ve > proven a complete IPv6 rollout can you get anymore IPv4" > > --- > Hendrik Visage > Instant messaging: https://t.me/hvisage > > >> On 13 Oct 2025, at 16:43, Andrew Alston wrote: >> >> Hi All, >> >> I was wondering if there were updated statistics for the amount of >> space allocated in the last 3 years.? In addition to this information >> regarding exactly how much free space is still available in the IPv4 >> unallocated pool (excluding reservations) >> >> I ask this because depending on the allocation rate - we may wish to >> consider revising the soft-landing policy that currently reserves a >> /12 worth of ipv4 space for "future uses, as yet unforeseen". >> >> I point out that the soft landing policy was ratified in 2011, and if >> we still, after 14 years, have not been able to articulate a clear >> reason for such a large reservation, I think it's time we look at >> most, if not all, of that /12 back into the main unallocated pool >> that can be allocated for African resource holders that actually need it. >> >> Amongst other reasons, sitting with unallocated, unannounced, >> reserved space like this leaves the space vulnerable to hijacking and >> malicious use or even potential theft. >> >> Thanks >> >> Andrew >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordi.palet at consulintel.es Thu Oct 16 07:37:58 2025 From: jordi.palet at consulintel.es (jordi.palet at consulintel.es) Date: Thu, 16 Oct 2025 09:37:58 +0200 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <1A569F83-1E16-46ED-949C-20D0C2E6F521@afrinic.net> References: <1A569F83-1E16-46ED-949C-20D0C2E6F521@afrinic.net> Message-ID: <993B1FB8-A403-4CD5-AB07-21447791F9B9@consulintel.es> Having worked in policy development, and with customers in all the RIRs, I can?t agree with that. You always think your country is the worst (at least that was my personal view about my own country before I started traveling), but then you discover that good and bad things happen everywhere, just different cultures, different views, where you may consider that some things are more or less important compared to another country or region. It is true that if you compare ?the global south? vs ?the global north?, it may seem that one is less advanced that the other, and it may be even true for example in terms of broadband availability, but there are, for example, several ISPs in South America that are more advanced in terms of IPv6 deployment than in other countries in the EU (including Spain). All is a matter of when, so yes, the difference is timing, nothing else nothing less. This is also the reason, for example, policies in the RIRs are very equivalent in the different regions, some times, with some delays (like it happened in Afrinic with transfers, same it where a bit later in LACNIC compared with the other RIRs). I think if you start thinking ?Africa? is different, is worst or something like that, you create the problem, so please, don?t assume that. Regards, Jordi @jordipalet > El 15 oct 2025, a las 20:41, Ben Roberts - AfriNIC via RPD escribi?: > > > 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. > > ++1 > Sent from my iPhone > >> On 15 Oct 2025, at 20:13, Sami Salih wrote: >> >> >> 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.roberts at afrinic.net Thu Oct 16 07:47:14 2025 From: ben.roberts at afrinic.net (Ben Roberts - AfriNIC) Date: Thu, 16 Oct 2025 10:47:14 +0300 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <993B1FB8-A403-4CD5-AB07-21447791F9B9@consulintel.es> References: <993B1FB8-A403-4CD5-AB07-21447791F9B9@consulintel.es> Message-ID: Jordi, Haven worked in network building and leading the tech teams that accomplished building 110,000 km of fibre, some of the biggest data centres in Africa, and (arguably ) the largest IP network backbones in the continent, I would say my experience is more than a tourist, and I confirm my support for Sami?s comment based on 20 years of hard work. Sent from my iPhone > On 16 Oct 2025, at 10:39, jordi.palet--- via RPD wrote: > > ?Having worked in policy development, and with customers in all the RIRs, I can?t agree with that. > > You always think your country is the worst (at least that was my personal view about my own country before I started traveling), but then you discover that good and bad things happen everywhere, just different cultures, different views, where you may consider that some things are more or less important compared to another country or region. > > It is true that if you compare ?the global south? vs ?the global north?, it may seem that one is less advanced that the other, and it may be even true for example in terms of broadband availability, but there are, for example, several ISPs in South America that are more advanced in terms of IPv6 deployment than in other countries in the EU (including Spain). > > All is a matter of when, so yes, the difference is timing, nothing else nothing less. This is also the reason, for example, policies in the RIRs are very equivalent in the different regions, some times, with some delays (like it happened in Afrinic with transfers, same it where a bit later in LACNIC compared with the other RIRs). > > I think if you start thinking ?Africa? is different, is worst or something like that, you create the problem, so please, don?t assume that. > > Regards, > Jordi > > @jordipalet > > >> El 15 oct 2025, a las 20:41, Ben Roberts - AfriNIC via RPD escribi?: >> >> >> 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. >> >> ++1 >> Sent from my iPhone >> >>> On 15 Oct 2025, at 20:13, Sami Salih wrote: >>> >>> >>> 1. The African context is fundamentally different from that of the global north, so we can?t simply mirror their approaches. This can be detailed in another thread if you don't agree, but for me it's obvious. >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Thu Oct 16 09:03:14 2025 From: owen at delong.com (Owen DeLong) Date: Thu, 16 Oct 2025 02:03:14 -0700 Subject: [rpd] Pushing IPv6 ? Re: Questions about IP Allocation rate In-Reply-To: <069b88a9-0762-479d-84cf-de4eed64520c@uls.co.za> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> <069b88a9-0762-479d-84cf-de4eed64520c@uls.co.za> Message-ID: <9DF19C1D-9F62-4AD7-B35E-9CA4BB35E819@delong.com> > On Oct 16, 2025, at 00:33, Jaco Kroon wrote: > > Hi Hendrik, > > I'm in two minds on this. On the one hand ... let it burn seems good. > > On the other hand, the single largest cheap hosting provider is SA still has no sensible plan on deploying IPv6 as far as I can tell, neither does any of the MNOs. > If they don?t by now, then actual runout is likely the only thing that will finally spur them to act. > The MNOs (at least two of them) claim they're ready, but no customer wants it ... and when the customers ask, they're being told it's in the roadmap but no timelines has been set since there's not high demand. > They are lying. This has been par for the course for 20+ years. In the early 2000s, I was staffing an ARIN booth at a trade show next to a software vendor that had a product for network monitoring. All day long, we?d hear people walk up, ask about IPv6 support in the product and be told ?None of our customers have expressed any interest.? About half of them walked away in dismay, the other half pointed out that this _WAS_ a customer expressing interest. The vendor seemed utterly impervious to the customer requests. > Doing v6-only on hosting side, and then using a small amount of v4 space to stateless NAT into the v6 infra is easy. There are rumours (good authority but I've not personally confirmed it) that Facebook does exactly this already, and given it's stateless I can imagine that. > Not a rumor. Facebook does something slightly different, but it has roughly the same effect (IIRC, they?re using transparent proxies to terminate the v4 and pass it along in v6). Facebook is all v6 behind the scenes and you get better performance if you arrive native v6. > My concern is getting CG-NAT just right is non-trivial, as anybody that provides services even marginally more complex than http will attest to. And given the above situation where hosting providers are reluctant to deploy IPv6 for some reason. > NAT of any form is a horrible ugly hack that has consistently and for all time it has existed provided more pain than good. If we don?t get provider off the stick to provide IPv6, CG-NAT is the future we will be stuck with. Worse, it?s going to likely be multi-layer CG-NAT and it?s only going to get uglier the longer we preserve the fallacious illusion that IPv4 must be the lingua franca of the internet and all sites must support v4 and v6 is optional. > INVARIABLY when we are for AAAA records for services run externally where we manage DNS, we're being told one of two things: > > 1. There's not IPv6 available; or > 2. Nobody cares about IPv6 so we don't bother. > > This seems like circular reasoning to me, nobody cares because nobody has it, and nobody has it because nobody cares. > It?s an excuse. It?s mainly a dunwanna problem. They don?t want to deal with it as long as there?s no forcing function. The ?global north? as I?ve heard it called elsewhere in this discussion isn?t ahead on this because of great foresight or better funding or better anticipation or more cooperative vendors. It?s ahead because the RIRs all ran out of IPv4 years ago and the lack of an IPv4 free pool and the high costs in the transfer market have served as a forcing function. > IPv6 for me seems more and more like the answer to IPv$ (which I differentiate from IPv4 ?). > What, exactly is the distinction? Is IPv$ the amount of money it costs you to continually add layers of hacks to keep your IPv4 network running? (That would make sense to me and if that?s the case, the longer IPv4 stays ?necessary?, the more IPv$ you?re going to have to spend.) > Reality is that there is only one way IPv6 will become a reality, and that's by letting IPv4 burn down and causing it to break. > Sad, but true. > Until customers can't get to stuff because no IPv6 nobody is going to care. > > The ONLY customers I've got asking for IPv6 are those with home cameras that streams ... typically using RTP of sorts, and here what ends up happening is that the camera suppliers are making boatloads of money thanks to IPv4 since that means they get to sell a platform, camera connects to platform, and streaming goes through platform (TURN protocol). The performance is poor, and given most of these I've investigated sits in HK - that also raises some privacy concerns about who has access to video feeds. > Yep. > When those customers gets IPv6 I get two positives: > > 1. Their streaming is more reliable (no NAT ... no need to TURN via HK, results in less jitter, less buffering, less freezing and skipping). > 2. Overall less bandwidth ... for some reason I haven't investigated yet. > Probably because of the number of packets and the number of times the payload(s) have to traverse your network in the Customer Camera <-> Customer UI Device vs. Customer Camera <-> Rendezvous Server in HK <-> Customer UI Device. Also, the Rendezvous server adds some overhead on each packet for encoding the customer identity, etc. that isn?t necessary on a direct stream. > On the one hand I like having happy customers (need IPv4 or else they can't get to www.{somerandomsite}.co.za). On the other hand, let it burn so we can stop having these discussions. > The first hand can be best addressed by convincing randomsites.co.za to make their content available on v6. Unfortunately, if they don?t by now, the only thing likely to spur that is when they start losing customers that can?t get IPv4 addresses to reach them or at least the customers start suffering the poor performance of NAT64/etc. Owen > > Kind regards, > Jaco > > On 2025/10/14 10:21, Hendrik Visage wrote: > >> Question: >> >> Shouldn?t we rather consider pushing IPv6 deployment assistance across Africa? ie. let the rest of the IPv4 go ASAP without much resistance instead of making this a begging/pleading/fighting game? >> >> ARIN (North America) & RIPE (Europe) serviced areas are way ahead of IPv6 roll outs, ?cause they don?t have any left, and looking at AfriNIC services countries, we are still have an abundance of IPv4, so IPv6 percentage roll outs are very low, and rathe we should be pushing to mirror the IPv6 percentage rollout and usage rather than fighting over the few remaining IPv4s if we want to grow digital rollouts. >> >> Perhaps even moving to a state of: ?You can have IPv6, once you?ve proven a complete IPv6 rollout can you get anymore IPv4" >> >> --- >> Hendrik Visage >> Instant messaging: https://t.me/hvisage >> >> >>> On 13 Oct 2025, at 16:43, Andrew Alston wrote: >>> >>> Hi All, >>> >>> I was wondering if there were updated statistics for the amount of space allocated in the last 3 years. In addition to this information regarding exactly how much free space is still available in the IPv4 unallocated pool (excluding reservations) >>> >>> I ask this because depending on the allocation rate - we may wish to consider revising the soft-landing policy that currently reserves a /12 worth of ipv4 space for "future uses, as yet unforeseen". >>> >>> I point out that the soft landing policy was ratified in 2011, and if we still, after 14 years, have not been able to articulate a clear reason for such a large reservation, I think it's time we look at most, if not all, of that /12 back into the main unallocated pool that can be allocated for African resource holders that actually need it. >>> >>> Amongst other reasons, sitting with unallocated, unannounced, reserved space like this leaves the space vulnerable to hijacking and malicious use or even potential theft. >>> >>> Thanks >>> >>> Andrew >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> >> --- >> >> Hendrik Visage >> >> hvisage at hevis.co.za >> >> HeViS.Co Systems Pty Ltd >> >> https://www.envisage.co.za >> >> >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Thu Oct 16 19:08:37 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Thu, 16 Oct 2025 21:08:37 +0200 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: References: <2cd1aca8-6c68-4ed0-8eb9-18835cf989a3@uls.co.za> Message-ID: <0568c801-0c37-47f9-a24b-c7de148cbabd@uls.co.za> Hi, > Your count of two prefixes originated by a different AS counts a /22 > superset and a /23 more specific in the same block. Perhaps we should > only count the largest aggregates (minimum equivalent prefixes) > announced by each non-matching ASN. Sorry if I was unclear.? We originate the /23, but it forms part of the larger /22, so the /23 should get counted here, but yes, if we also originated the two /24s or one of them only, all of that since it's more specifics of the /23 should only be counted once, so you're still right in that only the largest aggregates should be counted. > > As you pointed out, there are plenty of legitimate cases for this. For > example, some ISPs will issue space to multi-homed customers who will > then originate more specifics assigned to them from their own ASN > while the covering aggregate would be announced by the ISP, but not > the more specifics. I'd like to get an idea of prevalent this really is. Kind regards, Jaco > > Owen > > >> On Oct 16, 2025, at 00:03, Jaco Kroon wrote: >> >> ? >> >> Hi, >> >> Two notes from my side: >> >> 1.? Isn't this (in part) what the whole AS0 policy was about?? Such >> that space that's reserved/not issued by Afrinic can be protected?? >> (Having inherited previously abused space ... I'm 100% behind such a >> policy). >> >> 2.? Whilst I agree with Andrew that it's difficult to determine the >> exact Geographical location of originations, and I like his concept >> of looking at reserved/available ASNs, I do think something that >> makes an equal amount of sense is to get an idea of the space issued >> to an org not originated by that org ... there are legitimate cases >> (eg, we originate space on behalf of one of our customers, used >> exclusively by that client), so I'm more interested in cases like >> "space issued to org X originated from Y non-X ASNs" (ie, don't count >> space where both the ASN and the space is assigned to the same ORG).? >> As concrete examples: >> >> 154.73.32.0/22 => org: ORG-ULSC1-AFRINIC >> AS327767 => org: ORG-ULSC1-AFRINIC >> >> That need not be counted. >> >> 102.214.182.0/23 => 102.214.180.0/22 => org: ORG-DCC1-AFRINIC >> AS327767 => org: ORG-ULSC1-AFRINIC >> >> Count these cases, and group by ORG.? So the above would result in: >> >> ORG-DCC1-AFRINIC originates 1 prefix from 1 alternative ASN. >> >> Andrew - I'd be happy to assist with some code for counting this if >> you throw the base on github and don't mind making that dump of yours >> for the DFZ data available. >> >> Kind regards, >> Jaco >> >> On 2025/10/15 14:35, Fernando Frediani wrote: >>> >>> Yeah it could be, but I would say that alone is already something >>> that can bring attention to resources because it is not what is >>> widely expected. I would easily believe that a fair amount of space >>> announce by other ASNs other than the one linked to it in the whois >>> may not be what was desired or justified at the same resources were >>> allocated. There are valid examples as you mentioned, but I would >>> say they are the fewer. >>> >>> I think the most important in this context is find out if the >>> resources are being use in Africa or not which it is slightly more >>> complex to asses than matching with whois data. >>> >>> Fernando >>> >>> On 10/15/2025 9:24 AM, Andrew Alston wrote: >>>> Hi Fernando, >>>> >>>> It's unfortunately extremely difficult to do this - because while >>>> an ASN may be allocated by AfriNIC it could be announced from >>>> anywhere, and even in the case of where an ASN is allocated by >>>> RIPE, it may be used in Africa to announce AfriNIC space (Liquid >>>> Telecom is an example of this, where 30844 is a RIPE ASN but almost >>>> all the space under it is afrinic allocated and announced in Africa). >>>> >>>> It would be possible to extend the code I wrote to show the source >>>> ASN of the prefix's?that are reserved - and then potentially to >>>> match that against other AfriNIC data to show who the ASN is owned >>>> by (if the ASN itself is allocated, in my verification I found that >>>> many of these prefix's are being announced by ASN's that are marked >>>> as available or reserved) >>>> >>>> I will see what I can do about adding that extra code at some point >>>> when I find the time. >>>> >>>> Thanks >>>> >>>> Andrew >>>> >>>> >>>> On Wed, Oct 15, 2025 at 3:14?PM Fernando Frediani >>>> wrote: >>>> >>>> Would it be possible to get detailed information about AfriNic >>>> prefixes that are currently being announced by different ASNs >>>> they are linked to and potentially being used out of the Africa >>>> region as well ? That would be a pretty interesting information >>>> to see. >>>> >>>> Regards >>>> Fernando >>>> >>>> On 10/15/2025 8:40 AM, Andrew Alston wrote: >>>>> Hi Guys, >>>>> >>>>> So - Firstly a few notes on using the code I'm going to paste >>>>> below. >>>>> >>>>> I created the BGP dump file on a juniper router by running a >>>>> "show route protocol bgp | save bgp.dump.txt" and then copying >>>>> that dump file to my local system from the Juniper router.? >>>>> Note - this produces a roughly 400meg file on a full table >>>>> router and it takes quite a while to run the command. >>>>> Then - I used the delegated-afrinic-extended-latest file >>>>> downloaded from the stats ftp server. >>>>> >>>>> In the code below - if you wish to run similar - change the >>>>> char BGP_DUMP[256] and char AFRINIC_EXT[256] global variables >>>>> to match the pathing to the relevant files. >>>>> >>>>> Note that there is some weirdness?in this code to deal with >>>>> endianness - and I will openly admit its not the cleanest (or >>>>> probably most efficient) code - but it does work and I've >>>>> verified the results. >>>>> >>>>> I've pasted the code below the results section. >>>>> >>>>> So - first the results: >>>>> >>>>> Found 824064 total available addresses and 4482304 total >>>>> reserved addresses >>>>> 41.57.124.0/22 fell between reserved >>>>> range 41.57.124.0 -> 41.57.127.255 [Adding 1024 addresses to >>>>> potential hijack] >>>>> 41.57.124.0/23 fell between reserved >>>>> range 41.57.124.0 -> 41.57.127.255 [Adding 512 addresses to >>>>> potential hijack] >>>>> 41.57.124.0/24 fell between reserved >>>>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.57.125.0/24 fell between reserved >>>>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.57.126.0/24 fell between reserved >>>>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.57.127.0/24 fell between reserved >>>>> range 41.57.124.0 -> 41.57.127.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.77.64.0/21 fell between reserved >>>>> range 41.77.64.0 -> 41.77.71.255 [Adding 2048 addresses to >>>>> potential hijack] >>>>> 41.138.192.0/24 fell between reserved >>>>> range 41.138.192.0 -> 41.138.223.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.224.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.225.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.226.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.227.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.228.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.229.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.230.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.231.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.232.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.233.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.234.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.235.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.236.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.237.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.238.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.239.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.240.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.241.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.242.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.243.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.244.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.245.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.246.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.247.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.248.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.249.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.250.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.251.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.254.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.204.255.0/24 fell between reserved >>>>> range 41.204.224.0 -> 41.204.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.205.224.0/19 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 8192 addresses to >>>>> potential hijack] >>>>> 41.205.225.0/24 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.205.232.0/24 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.205.234.0/24 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.205.235.0/24 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.205.237.0/24 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.205.238.0/24 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.205.239.0/24 fell between reserved >>>>> range 41.205.224.0 -> 41.205.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 41.220.48.0/20 fell between reserved >>>>> range 41.220.48.0 -> 41.220.63.255 [Adding 4096 addresses to >>>>> potential hijack] >>>>> 80.88.6.0/24 fell between reserved range >>>>> 80.88.6.0 -> 80.88.6.255 [Adding 256 addresses to potential >>>>> hijack] >>>>> 102.128.74.0/24 fell between reserved >>>>> range 102.128.72.0 -> 102.128.75.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 102.135.164.0/24 fell between >>>>> reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 102.135.165.0/24 fell between >>>>> reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 102.135.166.0/24 fell between >>>>> reserved range 102.135.164.0 -> 102.135.167.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 102.219.128.0/24 fell between >>>>> reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 102.219.129.0/24 fell between >>>>> reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 102.219.130.0/24 fell between >>>>> reserved range 102.219.128.0 -> 102.219.131.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 102.221.148.0/22 fell between >>>>> reserved range 102.221.144.0 -> 102.221.151.255 [Adding 1024 >>>>> addresses to potential hijack] >>>>> 156.0.254.0/24 fell between reserved >>>>> range 156.0.254.0 -> 156.0.254.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 160.119.208.0/24 fell between >>>>> reserved range 160.119.208.0 -> 160.119.211.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 160.119.209.0/24 fell between >>>>> reserved range 160.119.208.0 -> 160.119.211.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 164.160.192.0/21 fell between >>>>> reserved range 164.160.192.0 -> 164.160.223.255 [Adding 2048 >>>>> addresses to potential hijack] >>>>> 169.255.164.0/22 fell between >>>>> reserved range 169.255.164.0 -> 169.255.167.255 [Adding 1024 >>>>> addresses to potential hijack] >>>>> 193.188.7.0/24 fell between reserved >>>>> range 193.188.7.0 -> 193.188.7.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.13.203.0/24 fell between reserved >>>>> range 196.13.203.0 -> 196.13.203.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.20.60.0/24 fell between reserved >>>>> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.20.61.0/24 fell between reserved >>>>> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.20.62.0/24 fell between reserved >>>>> range 196.20.32.0 -> 196.20.63.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.41.74.0/24 fell between reserved >>>>> range 196.41.74.0 -> 196.41.74.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.43.252.0/24 fell between reserved >>>>> range 196.43.252.0 -> 196.43.252.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.46.18.0/24 fell between reserved >>>>> range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.46.19.0/24 fell between reserved >>>>> range 196.46.18.0 -> 196.46.19.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.46.152.0/24 fell between reserved >>>>> range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.46.153.0/24 fell between reserved >>>>> range 196.46.152.0 -> 196.46.159.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.46.154.0/23 fell between reserved >>>>> range 196.46.152.0 -> 196.46.159.255 [Adding 512 addresses to >>>>> potential hijack] >>>>> 196.50.21.0/24 fell between reserved >>>>> range 196.50.21.0 -> 196.50.21.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.53.113.0/24 fell between reserved >>>>> range 196.52.0.0 -> 196.55.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.54.72.0/23 fell between reserved >>>>> range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to >>>>> potential hijack] >>>>> 196.55.102.0/23 fell between reserved >>>>> range 196.52.0.0 -> 196.55.255.255 [Adding 512 addresses to >>>>> potential hijack] >>>>> 196.63.243.0/24 fell between reserved >>>>> range 196.62.0.0 -> 196.63.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.195.4.0/24 fell between reserved >>>>> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.195.15.0/24 fell between reserved >>>>> range 196.194.0.0 -> 196.195.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 196.195.253.0/24 fell between >>>>> reserved range 196.194.0.0 -> 196.195.255.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 197.157.200.0/22 fell between >>>>> reserved range 197.157.200.0 -> 197.157.203.255 [Adding 1024 >>>>> addresses to potential hijack] >>>>> 197.231.248.0/22 fell between >>>>> reserved range 197.231.248.0 -> 197.231.251.255 [Adding 1024 >>>>> addresses to potential hijack] >>>>> 197.231.248.0/24 fell between >>>>> reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 197.231.249.0/24 fell between >>>>> reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 197.231.250.0/24 fell between >>>>> reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 197.231.251.0/24 fell between >>>>> reserved range 197.231.248.0 -> 197.231.251.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 197.234.208.0/24 fell between >>>>> reserved range 197.234.208.0 -> 197.234.215.255 [Adding 256 >>>>> addresses to potential hijack] >>>>> 212.12.224.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.225.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.226.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.227.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.229.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.231.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.232.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.233.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.234.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.235.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.236.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.237.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.238.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.239.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.240.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.241.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.242.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.243.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.244.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.245.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.246.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.247.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.248.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.249.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.250.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.251.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.252.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.254.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> 212.12.255.0/24 fell between reserved >>>>> range 212.12.224.0 -> 212.12.255.255 [Adding 256 addresses to >>>>> potential hijack] >>>>> Found 50176 potentially hijacked addresses >>>>> >>>>> --- Below here is the code (I didn't know if I could send >>>>> attachments to the RPD list so I just pasted the code >>>>> straight) --- >>>>> >>>>> // >>>>> // ?main.c >>>>> // ?AfrinicAudit >>>>> // >>>>> // ?Created by Andrew Alston on 15/10/2025. >>>>> // ?Code is considered open use with no restrictions. >>>>> // >>>>> >>>>> #include >>>>> #include >>>>> #include >>>>> #include >>>>> >>>>> char BGP_DUMP[256] = "/Users/aalston/audit/bgp.dump.txt"; >>>>> char AFRINIC_EXT[256] = >>>>> "/Users/aalston/audit/delegated-afrinic-extended-latest"; >>>>> >>>>> struct routes { >>>>> ? ? unsigned int network; >>>>> ? ? unsigned int broadcast; >>>>> ? ? unsigned int mask; >>>>> ? ? unsigned short cidr; >>>>> }; >>>>> >>>>> struct audit { >>>>> ? ? struct routes *dfz; >>>>> ? ? int dfz_count; >>>>> ? ? struct routes *reserved; >>>>> ? ? int total_resv; >>>>> ? ? int rc; >>>>> ? ? struct routes *available; >>>>> ? ? int total_avail; >>>>> ? ? int ac; >>>>> }; >>>>> >>>>> int parse_afrinic_extended(char *afext, struct audit *output) { >>>>> ? ? FILE *dump = fopen(afext, "r"); >>>>> ? ? if(!dump) >>>>> ? ? ? ? return -1; >>>>> ? ? char buffer[1024] = {0}; >>>>> ? ? char *delim; >>>>> ? ? output->rc = 0; >>>>> ? ? while(fgets(buffer, 1024, dump)) { >>>>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") >>>>> && strstr(buffer, "ipv4")) { >>>>> ? ? ? ? ? ? output->rc++; >>>>> ? ? ? ? } >>>>> ? ? } >>>>> ? ? output->reserved = calloc(output->rc, sizeof(struct routes)); >>>>> ? ? if(!output->reserved) >>>>> ? ? ? ? return -1; >>>>> ? ? output->rc = 0; >>>>> ? ? struct routes *resv = output->reserved; >>>>> ? ? rewind(dump); >>>>> ? ? while(fgets(buffer, 1024, dump)) { >>>>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "reserved") >>>>> && strstr(buffer, "ipv4")) { >>>>> ? ? ? ? ? ? delim = strtok(buffer, "|"); >>>>> ? ? ? ? ? ? for(int i = 0; i < 3; i++) >>>>> ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); >>>>> ? ? ? ? ? ? inet_pton(AF_INET, delim, &resv[output->rc].network); >>>>> ? ? ? ? ? ? resv[output->rc].network = >>>>> __builtin_bswap32(resv[output->rc].network); >>>>> ? ? ? ? ? ? delim = strtok(NULL, "|"); >>>>> ? ? ? ? ? ? unsigned int addr_count = atoi(delim); >>>>> ? ? ? ? ? ? output->total_resv += addr_count; >>>>> ? ? ? ? ? ? resv[output->rc].broadcast = >>>>> resv[output->rc].network+(addr_count-1); >>>>> ? ? ? ? ? ? resv[output->rc].network = >>>>> __builtin_bswap32(resv[output->rc].network); >>>>> ? ? ? ? ? ? resv[output->rc].broadcast = >>>>> __builtin_bswap32(resv[output->rc].broadcast); >>>>> ? ? ? ? ? ? resv[output->rc].mask = >>>>> ~__builtin_bswap32((unsigned int)addr_count-1); >>>>> ? ? ? ? ? ? output->rc++; >>>>> ? ? ? ? } >>>>> ? ? } >>>>> ? ? rewind(dump); >>>>> ? ? while(fgets(buffer, 1024, dump)) { >>>>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") >>>>> && strstr(buffer, "ipv4")) { >>>>> ? ? ? ? ? ? output->ac++; >>>>> ? ? ? ? } >>>>> ? ? } >>>>> ? ? output->available = calloc(output->ac, sizeof(struct routes)); >>>>> ? ? if(!output->available) >>>>> ? ? ? ? return -1; >>>>> ? ? struct routes *avail = output->available; >>>>> ? ? rewind(dump); >>>>> ? ? while(fgets(buffer, 1024, dump)) { >>>>> ? ? ? ? if(strstr(buffer, "ZZ") && strstr(buffer, "available") >>>>> && strstr(buffer, "ipv4")) { >>>>> ? ? ? ? ? ? delim = strtok(buffer, "|"); >>>>> ? ? ? ? ? ? for(int i = 0; i < 3; i++) >>>>> ? ? ? ? ? ? ? ? delim = strtok(NULL, "|"); >>>>> ? ? ? ? ? ? inet_pton(AF_INET, delim, &avail[output->ac].network); >>>>> ? ? ? ? ? ? avail[output->ac].network = >>>>> __builtin_bswap32(avail[output->ac].network); >>>>> ? ? ? ? ? ? delim = strtok(NULL, "|"); >>>>> ? ? ? ? ? ? unsigned int addr_count = atoi(delim); >>>>> ? ? ? ? ? ? output->total_avail += addr_count; >>>>> ? ? ? ? ? ? avail[output->ac].broadcast = >>>>> avail[output->ac].network+(addr_count-1); >>>>> ? ? ? ? ? ? avail[output->ac].mask = >>>>> ~__builtin_bswap32((unsigned int)addr_count-1); >>>>> ? ? ? ? ? ? output->ac++; >>>>> ? ? ? ? } >>>>> ? ? } >>>>> ? ? fclose(dump); >>>>> ? ? return 0; >>>>> } >>>>> >>>>> int parse_dfz(char *dfz_dump, struct audit *output) { >>>>> ? ? FILE *dump = fopen(dfz_dump, "r"); >>>>> ? ? char buffer[1024] = {0}; >>>>> ? ? int rc = 0, mult = 0, cidr = 0; >>>>> ? ? char *delim; >>>>> ? ? if(!dump) { >>>>> ? ? ? ? return -1; >>>>> ? ? } >>>>> ? ? while(fgets(buffer, 1024, dump)) { >>>>> ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9' && >>>>> strtok(buffer, "/") && strchr(buffer, '.')) { >>>>> ? ? ? ? ? ? rc++; >>>>> ? ? ? ? } >>>>> ? ? } >>>>> ? ? output->dfz = calloc(rc, sizeof(struct routes)); >>>>> ? ? output->dfz_count = rc; >>>>> ? ? if(!output->dfz) { >>>>> ? ? ? ? return -1; >>>>> ? ? } >>>>> ? ? rewind(dump); >>>>> ? ? rc = 0; >>>>> ? ? while(fgets(buffer, 1024, dump)) { >>>>> ? ? ? ? if(buffer[0] >= '1' && buffer[0] <= '9') { >>>>> ? ? ? ? ? ? cidr = 0; >>>>> ? ? ? ? ? ? delim = strtok(buffer, "/"); >>>>> ? ? ? ? ? ? delim = strtok(NULL, "/"); >>>>> ? ? ? ? ? ? if(!delim) { >>>>> ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); >>>>> ? ? ? ? ? ? ? ? continue; >>>>> ? ? ? ? ? ? } >>>>> ? ? ? ? ? ? mult = 1; >>>>> ? ? ? ? ? ? for(int i = 0; i < 3; i++) { >>>>> ? ? ? ? ? ? ? ? if(delim[i] >= '0' && delim[i] <= '9') { >>>>> ? ? ? ? ? ? ? ? ? ? cidr = cidr * mult+(9-('9'-delim[i])); >>>>> ? ? ? ? ? ? ? ? ? ? mult*=10; >>>>> ? ? ? ? ? ? ? ? } >>>>> ? ? ? ? ? ? } >>>>> ? ? ? ? ? ? delim = strchr(buffer, '.'); >>>>> ? ? ? ? ? ? if(!delim) { >>>>> ? ? ? ? ? ? ? ? memset(buffer, 0, 1024); >>>>> ? ? ? ? ? ? ? ? continue; >>>>> ? ? ? ? ? ? } >>>>> ? ? ? ? ? ? output->dfz[rc].cidr = cidr; >>>>> ? ? ? ? ? ? inet_pton(AF_INET, buffer, &output->dfz[rc].network); >>>>> ? ? ? ? ? ? output->dfz[rc].cidr = cidr; >>>>> ? ? ? ? ? ? output->dfz[rc].network = >>>>> __builtin_bswap32((unsigned int)output->dfz[rc].network); >>>>> ? ? ? ? ? ? output->dfz[rc].mask = (~(unsigned int)0) << >>>>> (32-cidr); >>>>> ? ? ? ? ? ? output->dfz[rc].broadcast = >>>>> output->dfz[rc].network + ((~(unsigned int)0) >> cidr); >>>>> ? ? ? ? ? ? output->dfz[rc].network = >>>>> __builtin_bswap32((unsigned int)output->dfz[rc].network); >>>>> ? ? ? ? ? ? output->dfz[rc].broadcast = >>>>> __builtin_bswap32((unsigned int)output->dfz[rc].broadcast); >>>>> ? ? ? ? ? ? rc++; >>>>> ? ? ? ? ? ? memset(buffer, 0, 1024); >>>>> ? ? ? ? } >>>>> ? ? } >>>>> ? ? fclose(dump); >>>>> ? ? return 0; >>>>> } >>>>> >>>>> int audit_reserved(struct audit *data) { >>>>> ? ? int hijack_count = 0; >>>>> ? ? for(int i = 0; i < data->dfz_count; i++) { >>>>> ? ? ? ? unsigned int dfz_net = __builtin_bswap32((unsigned >>>>> int)data->dfz[i].network); >>>>> ? ? ? ? unsigned int dfz_bcast = __builtin_bswap32((unsigned >>>>> int)data->dfz[i].broadcast); >>>>> ? ? ? ? for(int r = 0; r < data->rc; r++) { >>>>> ? ? ? ? ? ? unsigned int resv_net = >>>>> __builtin_bswap32((unsigned int)data->reserved[r].network); >>>>> ? ? ? ? ? ? unsigned int resv_bcast = >>>>> __builtin_bswap32((unsigned int)data->reserved[r].broadcast); >>>>> ? ? ? ? ? ? if(dfz_net >= resv_net && dfz_net <= resv_bcast) { >>>>> ? ? ? ? ? ? ? ? hijack_count += ((dfz_bcast-dfz_net)+1); >>>>> ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; >>>>> ? ? ? ? ? ? ? ? char resv_network[INET_ADDRSTRLEN] = {0}; >>>>> ? ? ? ? ? ? ? ? char resv_broadcast[INET_ADDRSTRLEN] = {0}; >>>>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, >>>>> dfz_route, INET_ADDRSTRLEN); >>>>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->reserved[r].network, >>>>> resv_network, INET_ADDRSTRLEN); >>>>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, >>>>> &data->reserved[r].broadcast, resv_broadcast, INET_ADDRSTRLEN); >>>>> ? ? ? ? ? ? ? ? printf("%s/%d fell between reserved range %s >>>>> -> %s [Adding %d addresses to potential hijack]\n", >>>>> ? ? ? ? ? ? ? ? ? ? ? ?dfz_route, data->dfz[i].cidr, >>>>> resv_network, resv_broadcast, (dfz_bcast-dfz_net)+1); >>>>> ? ? ? ? ? ? } >>>>> ? ? ? ? } >>>>> ? ? ? ? for(int a = 0; a < data->ac; a++) { >>>>> ? ? ? ? ? ? unsigned int avail_net = >>>>> __builtin_bswap32((unsigned int)data->available[a].network); >>>>> ? ? ? ? ? ? unsigned int avail_bcast = >>>>> __builtin_bswap32((unsigned int)data->available[a].broadcast); >>>>> ? ? ? ? ? ? if(dfz_net >= data->available[a].network && >>>>> dfz_net <= data->available[a].broadcast) { >>>>> ? ? ? ? ? ? ? ? hijack_count += >>>>> ((data->available[a].broadcast-data->available[a].network)+1); >>>>> ? ? ? ? ? ? ? ? char dfz_route[INET_ADDRSTRLEN] = {0}; >>>>> ? ? ? ? ? ? ? ? char avail_network[INET_ADDRSTRLEN] = {0}; >>>>> ? ? ? ? ? ? ? ? char avail_broadcast[INET_ADDRSTRLEN] = {0}; >>>>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &data->dfz[i].network, >>>>> dfz_route, INET_ADDRSTRLEN); >>>>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_net, avail_network, >>>>> INET_ADDRSTRLEN); >>>>> ? ? ? ? ? ? ? ? inet_ntop(AF_INET, &avail_bcast, >>>>> avail_broadcast, INET_ADDRSTRLEN); >>>>> ? ? ? ? ? ? ? ? printf("%s/%d fell between available range %s >>>>> -> %s\n", dfz_route, data->dfz[i].cidr, avail_network, >>>>> avail_broadcast); >>>>> ? ? ? ? ? ? } >>>>> ? ? ? ? } >>>>> ? ? } >>>>> ? ? printf("Found %d potentially hijacked addresses\n", >>>>> hijack_count); >>>>> ? ? return 0; >>>>> } >>>>> >>>>> int main(int argc, const char * argv[]) { >>>>> ? ? struct audit data = {0}; >>>>> ? ? if(parse_dfz(BGP_DUMP, &data)) >>>>> ? ? ? ? return EXIT_FAILURE; >>>>> ? ? if(parse_afrinic_extended(AFRINIC_EXT, &data)) >>>>> ? ? ? ? return EXIT_FAILURE; >>>>> ? ? printf("Found %d total available addresses and %d total >>>>> reserved addresses\n", data.total_avail, data.total_resv); >>>>> ? ? audit_reserved(&data); >>>>> ? ? return EXIT_SUCCESS; >>>>> } >>>>> >>>>> _______________________________________________ >>>>> RPD mailing list >>>>> RPD at afrinic.net >>>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Thu Oct 16 19:26:04 2025 From: owen at delong.com (Owen DeLong) Date: Thu, 16 Oct 2025 12:26:04 -0700 Subject: [rpd] Reserved Space/Available Space and potential hijacking In-Reply-To: <0568c801-0c37-47f9-a24b-c7de148cbabd@uls.co.za> References: <2cd1aca8-6c68-4ed0-8eb9-18835cf989a3@uls.co.za> <0568c801-0c37-47f9-a24b-c7de148cbabd@uls.co.za> Message-ID: <67016857-1C77-41D8-B99D-2CBE1BE3287E@delong.com> >> >> As you pointed out, there are plenty of legitimate cases for this. For example, some ISPs will issue space to multi-homed customers who will then originate more specifics assigned to them from their own ASN while the covering aggregate would be announced by the ISP, but not the more specifics. > I'd like to get an idea of prevalent this really is. > To what end? It?s just one example of legitimate reasons that prefixes may be originated by ASNs that don?t belong to the resource holder. Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: From madomey at hotmail.com Fri Oct 17 01:00:20 2025 From: madomey at hotmail.com (Marcus K. G. Adomey) Date: Fri, 17 Oct 2025 01:00:20 +0000 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: <5DF5ED45-A4B2-4DEB-B279-A7C045495500@wacren.net> <44830741-6C2C-44D5-BBBA-369ACCF19838@yahoo.fr> Message-ID: Dear Owen, This confrontational and personalization approach, when a collective reflection is demanded, does not help Africa. Marcus ________________________________ From: Owen DeLong Sent: Thursday, October 16, 2025 3:35:10 AM To: Marcus K. G. Adomey Cc: Oaiya Omo ; Gr?goire EHOUMI ; rpd Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual This strikes me as a very superficial comment on that? Please, elaborate on what you view as the true root causes of the breakdown and the deeper wounds? If you want everyone else to commit to genuine reflection and impartial review, how about starting yourself? Owen On Oct 15, 2025, at 09:04, Marcus K. G. Adomey wrote: Dear PDWG Members, REFLECTION AND RENEWAL IN THE PDWG The PDWG is central to AfriNIC?s PDP, yet its effectiveness has declined due to breakdown in constructive dialogue. As we move forward, we must reflect on what went wrong ? both in our processes and group dynamics ? and how we can rebuild a respectful, inclusive, and professional environment fit for building consensus on policies. Unfortunately, current discussions remain superficial, failing to address the root causes of the breakdown. This approach leaves deeper wounds untreated and risks repeating past mistakes. Let us commit to genuine reflection and impartial review, so we can transform the PDWG into a resilient, transparent, and collaborative platform it was meant to be. Warm regards, Marcus ________________________________ From: Gr?goire EHOUMI via RPD Sent: Tuesday, October 14, 2025 1:46 PM To: Oaiya Omo Cc: rpd Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual Hello, On Oct 12, 2025, at 6:31?AM, Omo Oaiya via RPD wrote: ? It?s great to see discussion back on the list, a good sign that the community spirit is still strong. I agree with Owen. What really matters is that the feedback loop stays open, clear, and timely. On Ben?s point, participation will grow if we make the PDP more inclusive and relevant. We should bring in people from IXPs, NRENs, academia, civil society, and sectors shaping Africa?s digital economy. Linking policy work to that wider digital transformation agenda will draw new energy and perspectives. Let?s keep it going. Best, Omo ?More inclusive? by offering a pleasant, productive PDP to the expected standards, right ? Policy discussions and meetings have always been open to anyone to join and participate. No one has been prevented from participating in pdp, except perhaps our behaviours may have discouraged, scared away many people in our diverse and fragile ecosystem. The board made a key prerequisite to resumption of PDP as below: "A key prerequisite will be to ensure that all community mailing lists maintain an atmosphere of civility and constructive engagement." Governments are more attentive now, watching and assessing us. It shouldn't be like before thanks for our collective efforts. ?More relevant? yes towards policy making for Number resources management, but without turning the PDP into an IG forum? Community, members, board and staff should make sure that policies we discuss and approve serve the interests AFRICA and not private, personal interests. Cheers, - Gr?goire _______________________________________________ RPD mailing list RPD at afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From madhvi at afrinic.net Fri Oct 17 07:33:41 2025 From: madhvi at afrinic.net (Madhvi Gokool) Date: Fri, 17 Oct 2025 11:33:41 +0400 Subject: [rpd] Register for the "Updating ICP-2: Advancing Internet Number Governance for the Future" Webinar on 21st October 2025 In-Reply-To: References: Message-ID: <706c15f6-bfea-458b-b522-3df0311b7173@afrinic.net> Dear PDWG You may also find supplementary information on the ICP-2 Governance Document update? on our website https://www.afrinic.net/icp-2-review . We encourage to go through the second draft of the ?Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries ,? before the webinar and to also contribute your feedback on the ICP-2 Review mailing list . ?If not yet done, you need to first subscribe to the mailing list at https://lists.afrinic.net/mailman/listinfo/icp2-review , before you can submit your feedback. Kind Regards Madhvi Gokool www.afrinic.net On 15/10/2025 15:43, AFRINIC Announce via RPD wrote: > > Dear Colleagues, > > You are invited to register for the webinar on "Updating ICP-2: > Advancing Internet Number Governance for the Future"?Webinar. > > * > > *Date: Tuesday 21st October 2025* > > * > > *Time: 10:00 -11:00 UTC* > > * > > *Duration: 1:00 Hr * > > * > > *_Registration Link > _* > > The Internet Coordination Policy 2 (ICP-2 > ) > was developed in 2001 through the Address Supporting Organization > (ASO), with contributions from APNIC, ARIN, and RIPE NCC. Its purpose > was to establish criteria for the recognition of new Regional Internet > Registries (RIRs), serving as a framework to guide how RIRs are > recognized and maintained. > > For more than two decades, ICP-2 has been the implicit standard for > RIR accreditation and operations. However, the Internet ecosystem has > evolved considerably since then ? both in scale and in governance > complexity. Recognizing the need for modernization, the Number > Resource Organization Executive Council (NRO EC), together with the > Address Supporting Organization Address Council (ASO AC), launched an > initiative to review and update ICP-2 to better reflect today?s > realities. Among other discussions, the Council representatives will > give a summary of the main changes between the two versions of the RIR > Governance Documents and the rationale behind these changes. This > summary of changes is also _available on the NRO website > _ > > As part of this review process, the Number Resource Organization > Number Council (NRO NC) will host a webinar to share insights into the > next phase of the ICP-2 update. The session will introduce the second > draft of the ?Governance Document for the Recognition, Operation, and > Derecognition of Regional Internet Registries > ,? > which is intended to replace the original ICP-2. > > *Key Takeaways* > > * > > Gain a clear understanding of the ongoing process to update ICP-2, > a foundational policy that guides the recognition and operation of > Regional Internet Registries (RIRs). > > * > > Understand the rationale behind the proposed updates and how they > reflect today?s evolving Internet governance landscape. > > * > > Participate in the global consultation process. > > *_Secure your Spot Here > _* > > Be sure to save the date and spread the word as your participation is > key to making these sessions a success! > > ------------------------------------------------------------------------ > > Explore the full schedule and learn more about AFRINIC webinars on our > *_Webinar Series Page _*. > > We look forward to having you join us for these insightful sessions! > > ------------------------------------------------------------------------ > > Kind Regards, > > AFRINIC Communications. > > > > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Fri Oct 17 10:21:02 2025 From: owen at delong.com (Owen DeLong) Date: Fri, 17 Oct 2025 03:21:02 -0700 Subject: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual In-Reply-To: References: Message-ID: And yet you still have provided no useful details to supplement your rather superficial comment requesting others to dig deep. I?m just saying it would be good to practice what you preach and lead by example. Owen > On Oct 16, 2025, at 18:00, Marcus K. G. Adomey wrote: > > ? > Dear Owen, > > This confrontational and personalization approach, when a collective reflection is demanded, does not help Africa. > > > Marcus > > > From: Owen DeLong > Sent: Thursday, October 16, 2025 3:35:10 AM > To: Marcus K. G. Adomey > Cc: Oaiya Omo ; Gr?goire EHOUMI ; rpd > Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual > > This strikes me as a very superficial comment on that? Please, elaborate on what you view as the true root causes of the breakdown and the deeper wounds? > > If you want everyone else to commit to genuine reflection and impartial review, how about starting yourself? > > Owen > > >>> On Oct 15, 2025, at 09:04, Marcus K. G. Adomey wrote: >>> >>> Dear PDWG Members, >>> >>> REFLECTION AND RENEWAL IN THE PDWG >>> >>> The PDWG is central to AfriNIC?s PDP, yet its effectiveness has declined due to breakdown in constructive dialogue. As we move forward, we must reflect on what went wrong ? both in our processes and group dynamics ? and how we can rebuild a respectful, inclusive, and professional environment fit for building consensus on policies. >>> >>> Unfortunately, current discussions remain superficial, failing to address the root causes of the breakdown. This approach leaves deeper wounds untreated and risks repeating past mistakes. >>> >>> Let us commit to genuine reflection and impartial review, so we can transform the PDWG into a resilient, transparent, and collaborative platform it was meant to be. >>> >>> Warm regards, >>> >>> >>> Marcus >>> >>> From: Gr?goire EHOUMI via RPD >>> Sent: Tuesday, October 14, 2025 1:46 PM >>> To: Oaiya Omo >>> Cc: rpd >>> Subject: Re: [rpd] [Board-Discuss] Call for Action: Modernizing the AFRINIC Policy Manual >>> >>> Hello, >>> >>> On Oct 12, 2025, at 6:31?AM, Omo Oaiya via RPD wrote: >>> >>> ? >>> It?s great to see discussion back on the list, a good sign that the community spirit is still strong. I agree with Owen. What really matters is that the feedback loop stays open, clear, and timely. >>> On Ben?s point, participation will grow if we make the PDP more inclusive and relevant. We should bring in people from IXPs, NRENs, academia, civil society, and sectors shaping Africa?s digital economy. Linking policy work to that wider digital transformation agenda will draw new energy and perspectives. >>> Let?s keep it going. >>> Best, >>> Omo >> ?More inclusive? by offering a pleasant, productive PDP to the expected standards, right ? >> >> Policy discussions and meetings have always been open to anyone to join and participate. No one has been prevented from participating in pdp, except perhaps our behaviours may have discouraged, scared away many people in our diverse and fragile ecosystem. >> >> The board made a key prerequisite to resumption of PDP as below: >> "A key prerequisite will be to ensure that all community mailing lists maintain an atmosphere of civility and constructive engagement." >> >> Governments are more attentive now, watching and assessing us. >> It shouldn't be like before thanks for our collective efforts. >> >> ?More relevant? yes towards policy making for Number resources management, but without turning the PDP into an IG forum? Community, members, board and staff should make sure that policies we discuss and approve serve the interests AFRICA and not private, personal interests. >> >> Cheers, >> - >> Gr?goire >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms-announce at afrinic.net Tue Oct 21 06:46:21 2025 From: comms-announce at afrinic.net (AFRINIC Announce) Date: Tue, 21 Oct 2025 06:46:21 +0000 Subject: [rpd] Reminder : Register for the "Updating ICP-2: Advancing Internet Number Governance for the Future" Webinar on 21st October 2025 Message-ID: Dear Colleagues, Registration for the webinar on "Updating ICP-2: Advancing Internet Number Governance for the Future" is ongoing. * Date: Tuesday 21st October 2025 * Time: 10:00 -11:00 UTC * Duration: 1:00 Hr * Registration Link ________________________________ The session will be conducted by the members of the ASO Address Council members and the panel will include: * Mr. Herv? Cl?ment -Member, Number Resource Organization Number Council (NRO NC) * Mr. Andrei Robachevsky - Member, Number Resource Organization Number Council (NRO NC) * Ms. Constanze Burguer - Member, Number Resource Organization Number Council (NRO NC) * Mr. Maemura Akinori - Member, Number Resource Organization Number Council (NRO NC) ________________________________ The Internet Coordination Policy 2 (ICP-2) was developed in 2001 through the Address Supporting Organization (ASO), with contributions from APNIC, ARIN, and RIPE NCC. Its purpose was to establish criteria for the recognition of new Regional Internet Registries (RIRs), serving as a framework to guide how RIRs are recognized and maintained. For more than two decades, ICP-2 has been the implicit standard for RIR accreditation and operations. However, the Internet ecosystem has evolved considerably since then ? both in scale and in governance complexity. Recognizing the need for modernization, the Number Resource Organization Executive Council (NRO EC), together with the Address Supporting Organization Address Council (ASO AC), launched an initiative to review and update ICP-2 to better reflect today?s realities. Among other discussions, the Council representatives will give a summary of the main changes between the two versions of the RIR Governance Documents and the rationale behind these changes. This summary of changes is also available on the NRO website As part of this review process, the Number Resource Organization Number Council (NRO NC) will host a webinar to share insights into the next phase of the ICP-2 update. The session will introduce the second draft of the ?Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries,? which is intended to replace the original ICP-2. Key Takeaways * Gain a clear understanding of the ongoing process to update ICP-2, a foundational policy that guides the recognition and operation of Regional Internet Registries (RIRs). * Understand the rationale behind the proposed updates and how they reflect today?s evolving Internet governance landscape. * Participate in the global consultation process. Secure your Spot Here Be sure to save the date and spread the word as your participation is key to making these sessions a success! ________________________________ Explore the full schedule and learn more about AFRINIC webinars on our Webinar Series Page. We look forward to having you join us for these insightful sessions! ________________________________ Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms-announce at afrinic.net Tue Oct 21 09:46:56 2025 From: comms-announce at afrinic.net (AFRINIC Announce) Date: Tue, 21 Oct 2025 09:46:56 +0000 Subject: [rpd] AFRINIC Webinar Series Streaming Shortly! Message-ID: Dear Colleagues, The webinar on "Updating ICP-2: Advancing Internet Number Governance for the Future" is about to start. If you are yet to register for this webinar, please do so here. If you are unable to join us on Zoom, we will be streaming the webinar live on the AFRINIC Youtube Page here. We look forward to your participation in this exciting webinar series and hope to see you there. Kind Regards, AFRINIC Communications. -------------- next part -------------- An HTML attachment was scrubbed... URL: From comms at afrinic.net Thu Oct 23 11:49:12 2025 From: comms at afrinic.net (AFRINIC Communication) Date: Thu, 23 Oct 2025 15:49:12 +0400 Subject: [rpd] Call for volunteers on the NRO Number Council (NRO NC) / Address Council (ASO AC) Message-ID: [Version en fran?ais au bas] Dear AFRINIC members and community, The AFRINIC Board of Directors wishes to inform you that it is taking immediate steps to fill the vacancy on the NRO Number Council (NRO NC) / Address Council (ASO AC) to address this pressing need for AFRINIC representation in this forum. All the three seats in the NRO NC / ASO AC from the AFRINIC Service Region are presently vacant; two are elected by the community with staggered three-year terms. The third is appointed by the AFRINIC Board. The AFRINIC Board intends to appoint one community volunteer now. The election for the two other seats will take place in due course. The AFRINIC Board hereby calls for volunteers who wish to be considered for appointment to the ASO AC/NRO NC. The tenure of the new appointee on the NRO NC / ASO AC will end on 31st December 2026. The appointed representative will also serve as AFRINIC?s representative on the ICP2 Review Process, thereby ensuring continuity and effective participation in both initiatives. The responsibilities of the ASO AC/NRO NC include: ? Overseeing the Global Policy Development Process (GPDP). ? Providing recommendations to the ICANN Board concerning the recognition of new RIRs. ? Defining procedures to appoint Directors to serve in the ASO?s two seats (Seat 9 and Seat 10) on the ICANN Board of Directors and to serve on other ICANN bodies. ? Providing advice to the ICANN Board on Internet number resource allocation policy, in conjunction with the RIRs. ? Developing procedures for conducting business in support of their responsibilities, in particular for the appointment of an ASO AC Chair and definition of the Chair?s responsibilities. If you are interested in serving, volunteers for the NRO NC/ASO AC seat are invited to submit a brief biography as well as a statement of reasons (motivation) justifying your application for appointment to the Senior Executive Assistant at: guylaine at afrinic.net Submissions must be received no later than 23:59 UTC on Thursday, 30 October 2025. On behalf of AFRINIC, we thank you beforehand for your cooperation and apologise for this short notice. AFRINIC appreciates your continued support in its endeavour to move ahead in the attainment of its objectives as the RIR for Africa. Kind Regards, Prof Adewale Adedokun Chairman AFRINIC Board of Directors ?????????????????????????????????? Chers membres et communaut? AFRINIC, Le conseil d'administration d'AFRINIC souhaite vous informer qu'il entreprend imm?diatement des mesures pour pourvoir le poste vacant au sein du NRO Number Council (NRO NC) / Address Council (ASO AC) afin de r?pondre ? ce besoin urgent de repr?sentation d'AFRINIC dans ce forum. Les trois si?ges du NRO NC / ASO AC de la r?gion de service AFRINIC sont actuellement vacants ; deux sont ?lus par la communaut? pour un mandat ?chelonn? de trois ans. Le troisi?me est nomm? par le conseil d'administration d'AFRINIC. Le conseil d'administration d'AFRINIC a l'intention de nommer d?s maintenant un volontaire de la communaut?. L'?lection pour les deux autres si?ges aura lieu en temps voulu. Le conseil d'administration d'AFRINIC lance donc un appel ? candidatures pour les volontaires qui souhaitent ?tre pris en consid?ration pour une nomination ? l'ASO AC/NRO NC. Le mandat du nouveau membre nomm? au NRO NC / ASO AC prendra fin le 31 d?cembre 2026. Le repr?sentant nomm? servira ?galement de repr?sentant d'AFRINIC dans le cadre du processus de r?vision de l'ICP2, assurant ainsi la continuit? et la participation effective aux deux initiatives. Les responsabilit?s de l'ASO AC/NRO NC comprennent : Superviser le processus mondial d'?laboration des politiques (GPDP). Fournir des recommandations au conseil d'administration de l'ICANN concernant la reconnaissance de nouveaux RIR. D?finir les proc?dures de nomination des directeurs qui occuperont les deux si?ges de l'ASO (si?ges 9 et 10) au conseil d'administration de l'ICANN et si?geront dans d'autres organes de l'ICANN. Conseiller le Conseil d'administration de l'ICANN sur la politique d'attribution des ressources de num?ros Internet, en collaboration avec les RIR. ?laborer des proc?dures pour mener ? bien leurs activit?s dans le cadre de leurs responsabilit?s, en particulier pour la nomination d'un pr?sident de l'ASO AC et la d?finition des responsabilit?s de ce dernier. Si vous souhaitez vous porter volontaire pour occuper un si?ge au NRO NC/ASO AC, veuillez envoyer une br?ve biographie ainsi qu'une lettre de motivation justifiant votre candidature ? l'adresse suivante : guylaine at afrinic.net Les candidatures doivent ?tre re?ues au plus tard le jeudi 30 octobre 2025 ? 23 h 59 UTC. Au nom d'AFRINIC, nous vous remercions par avance de votre coop?ration et vous prions de nous excuser pour ce d?lai tr?s court. AFRINIC appr?cie votre soutien continu dans ses efforts pour atteindre ses objectifs en tant que RIR pour l'Afrique. Cordialement, Prof Adewale Adedokun Pr?sident Conseil d'administration d'AFRINIC -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Fri Oct 24 10:45:11 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Fri, 24 Oct 2025 13:45:11 +0300 Subject: [rpd] AfriNIC audit data Message-ID: Hi All, While I haven't got around to publishing the code behind this - mainly because it by necessity exposes certain data and requires a BGP dump from a juniper router which is hundreds of megs big, I've attached the output of the code I wrote. One caveat with this data - There is nothing inherently wrong with space allocated to an organisation being announced by a non-AfriNIC ASN, there are many legitimate cases and reasons behind this. The same thing happens when space is allocated to one organisation but announced by another, and this can happen when a sub-company of a parent company is announcing space from their own ASN when the space was originally allocated to the parent. As such, when reading this data, it's important to understand that the abnormalities detected do not necessarily indicate anything nefarious - and this data should not be seen as accusations of malfeasance against anyone. Let's see if the lists let this post through! Thanks Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- Parsing organisation objects Parsing inetnum objects INET Object 196.216.2.0 - 196.216.3.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.0.0.0 - 196.255.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 41.0.0.0 - 41.255.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.0.0 - 196.1.0.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.2.3.0 - 196.2.3.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.0.0.0 - 154.255.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.216.168.0 - 196.216.168.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.216.169.0 - 196.216.169.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 197.0.0.0 - 197.255.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 105.0.0.0 - 105.255.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 102.0.0.0 - 102.255.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.10.0.0 - 154.10.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.33.0.0 - 154.33.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.34.0.0 - 154.34.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.1.0 - 196.1.1.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.68.0 - 196.1.68.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.104.0 - 196.1.104.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.105.0 - 196.1.105.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.106.0 - 196.1.106.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.108.0 - 196.1.108.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.109.0 - 196.1.109.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.110.0 - 196.1.111.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.113.0 - 196.1.113.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.114.0 - 196.1.114.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.134.0 - 196.1.134.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.65.0 - 196.3.65.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.72.0 - 196.3.72.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.12.32.0 - 196.12.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.15.16.0 - 196.15.31.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.1.0.0 - 154.1.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.2.0.0 - 154.2.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.3.0.0 - 154.3.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.4.0.0 - 154.4.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.5.0.0 - 154.5.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.6.0.0 - 154.6.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.7.0.0 - 154.7.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.9.0.0 - 154.9.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.11.0.0 - 154.11.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.12.0.0 - 154.12.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.13.0.0 - 154.13.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.17.0.0 - 154.17.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.18.0.0 - 154.18.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.19.0.0 - 154.19.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.20.0.0 - 154.20.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.21.0.0 - 154.21.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.22.0.0 - 154.22.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.23.0.0 - 154.23.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.24.0.0 - 154.24.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.25.0.0 - 154.25.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.26.0.0 - 154.26.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.27.0.0 - 154.27.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.28.0.0 - 154.28.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.29.0.0 - 154.29.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.30.0.0 - 154.30.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.31.0.0 - 154.31.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.35.0.0 - 154.35.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.36.0.0 - 154.36.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.37.0.0 - 154.37.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.38.0.0 - 154.38.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.39.0.0 - 154.39.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.40.0.0 - 154.40.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.41.0.0 - 154.41.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.42.0.0 - 154.42.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.43.0.0 - 154.43.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.44.0.0 - 154.44.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.45.0.0 - 154.45.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.46.0.0 - 154.46.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.47.0.0 - 154.47.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.48.0.0 - 154.48.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.49.0.0 - 154.49.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.50.0.0 - 154.50.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.51.0.0 - 154.51.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.52.0.0 - 154.52.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.53.0.0 - 154.53.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.54.0.0 - 154.54.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.55.0.0 - 154.55.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.56.0.0 - 154.56.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.57.0.0 - 154.57.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.58.0.0 - 154.58.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.59.0.0 - 154.59.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.60.0.0 - 154.60.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.61.0.0 - 154.61.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.62.0.0 - 154.62.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.63.0.0 - 154.63.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.64.0.0 - 154.64.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.2.0 - 196.1.2.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.72.0 - 196.1.73.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.107.0 - 196.1.107.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.136.0 - 196.1.136.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.138.0 - 196.1.139.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.140.0 - 196.1.140.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.141.0 - 196.1.141.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.142.0 - 196.1.142.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.160.0 - 196.1.175.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.2.0.0 - 196.2.0.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.2.1.0 - 196.2.1.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.0.0 - 196.3.7.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.8.0 - 196.3.11.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.12.0 - 196.3.13.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.32.0 - 196.3.47.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.48.0 - 196.3.55.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.56.0 - 196.3.56.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.73.0 - 196.3.73.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.95.0 - 196.3.95.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.104.0 - 196.3.104.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.153.0 - 196.3.153.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.184.0 - 196.3.191.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.192.0 - 196.3.223.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.4.46.0 - 196.4.47.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.4.48.0 - 196.4.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.4.64.0 - 196.4.67.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.4.68.0 - 196.4.69.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.4.70.0 - 196.4.70.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.12.0.0 - 196.12.7.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.12.8.0 - 196.12.9.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.12.64.0 - 196.12.127.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.12.160.0 - 196.12.191.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.27.0.0 - 196.27.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.28.48.0 - 196.28.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.32.0.0 - 196.32.7.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.32.128.0 - 196.32.159.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.42.0.0 - 196.42.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.216.1.0 - 196.216.1.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.112.0 - 196.1.112.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.135.0 - 196.1.135.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.16.0 - 196.3.31.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.74.0 - 196.3.75.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.76.0 - 196.3.79.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.80.0 - 196.3.87.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.88.0 - 196.3.89.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.106.0 - 196.3.106.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.132.0 - 196.3.135.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.136.0 - 196.3.143.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.144.0 - 196.3.147.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.152.0 - 196.3.152.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.29.64.0 - 196.29.95.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.32.32.0 - 196.32.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.32.64.0 - 196.32.95.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.40.0.0 - 196.40.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.40.64.0 - 196.40.95.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.8.0.0 - 154.8.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.14.0.0 - 154.14.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.15.0.0 - 154.15.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 154.32.0.0 - 154.32.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.3.0 - 196.1.3.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.5.0 - 196.1.5.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.6.0 - 196.1.6.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.64.0 - 196.1.67.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.69.0 - 196.1.69.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.1.70.0 - 196.1.70.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.2.4.0 - 196.2.7.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.66.0 - 196.3.66.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.91.0 - 196.3.91.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.15.32.0 - 196.15.63.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.3.67.0 - 196.3.71.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.192.140.0 - 196.192.143.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 45.192.0.0 - 45.222.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.192.124.0 - 196.192.124.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.192.112.0 - 196.192.113.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.49.0.0 - 196.49.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.60.0.0 - 196.60.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.223.0.0 - 196.223.31.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.223.32.0 - 196.223.47.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 102.224.0.0 - 102.239.255.255 matched skipped organisation ORG-AFNC1-AFRINIC INET Object 196.192.114.0 - 196.192.115.255 matched skipped organisation ORG-AFNC1-AFRINIC Processing to remove de-aggregates with no organisational assignment Done.... Parsing autonomous system number objects Allocated for 2621 autonomous system objects Parsing DFZ Found 824064 total available addresses and 4482304 total reserved addresses Starting matching of DFZ Routes to AfriNIC inetnum objects - go make a pizza, this takes a while Done Route 41.32.0.0/12 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.32.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.32.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.33.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.33.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.33.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.34.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.35.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.36.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.64.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.37.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.38.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.39.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.39.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.39.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.39.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.40.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.41.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.42.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.43.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.44.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.45.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.46.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.47.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.59.251.0/24 [AS327795] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TTCL1-AFRINIC [TANZANIA TELECOMMUNICATIONS CO. LTD] but owned by ORG-TeA1-AFRINIC [e-Government Authority] Route 41.59.252.0/22 [AS327795] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TTCL1-AFRINIC [TANZANIA TELECOMMUNICATIONS CO. LTD] but owned by ORG-TeA1-AFRINIC [e-Government Authority] Route 41.60.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.0.0/20 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 41.60.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.10.0/23 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 41.60.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.16.0/21 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 41.60.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65510] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.32.0/21 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.40.0/21 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.48.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.52.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS56696] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.56.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.58.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.60.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.62.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.64.0/18 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.64.0/19 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.96.0/19 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.128.0/22 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 41.60.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.132.0/24 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 41.60.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.150.0/23 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.60.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.192.0/22 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 41.60.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.206.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.60.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.228.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.230.0/24 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 41.60.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.236.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.238.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.60.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.64.0.0/16 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.2.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.24.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.32.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.40.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.52.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.56.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.70.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.170.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.172.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.176.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.191.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.192.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.194.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.64.195.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.0.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.1.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.2.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.3.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.4.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.6.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.10.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.14.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.16.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.17.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.18.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.19.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.25.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.26.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.29.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.30.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.31.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.32.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.33.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.34.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.35.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.36.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.38.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.39.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.40.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.45.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.47.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.49.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.51.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.53.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.55.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.56.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.57.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.59.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.60.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.61.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.62.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.64.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.65.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.66.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.67.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.69.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.73.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.74.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.75.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.78.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.79.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.80.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.81.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.84.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.85.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.86.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.94.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.98.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.101.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.103.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.104.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.105.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.108.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.109.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.111.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.112.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.113.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.114.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.116.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.117.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.118.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.119.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.121.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.122.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.123.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.128.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.129.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.131.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.132.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.135.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.137.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.138.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.139.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.141.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.142.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.143.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.144.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.145.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.146.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.147.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.149.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.150.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.151.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.152.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.153.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.155.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.157.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.158.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.160.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.161.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.162.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.163.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.165.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.166.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.168.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.170.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.171.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.172.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.173.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.174.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.176.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.181.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.182.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.183.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.184.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.185.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.186.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.188.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.192.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.194.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.197.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.200.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.201.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.205.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.208.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.209.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.210.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.212.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.213.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.214.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.215.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.216.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.218.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.219.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.221.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.222.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.223.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.224.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.225.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.226.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.227.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.228.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.229.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.230.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.231.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.232.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.233.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.234.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.235.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.237.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.238.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.239.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.240.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.241.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.242.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.243.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.244.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.245.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.246.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.247.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.248.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.249.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.250.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.251.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.252.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.253.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.254.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.65.255.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.66.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51265] Prefix was owned by ORG-BA1-AFRINIC [BCS Group (BCSNet)] Route 41.71.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.71.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.71.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.71.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.71.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.71.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.72.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.72.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.72.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.73.158.0/24 [AS37350] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA74-AFRINIC [IS InternetSolutions Limited] but owned by ORG-IISG1-AFRINIC [Dimension Data Ltd] Route 41.73.244.0/24 [AS328290] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GTN1-AFRINIC [Inq. Digital Nigeria] but owned by ORG-VBCD1-AFRINIC [INQ Cote d'Ivoire] Route 41.74.160.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.160.0/21 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.160.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.160.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.163.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.164.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.164.0/23 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.166.0/23 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.166.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.167.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.168.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.168.0/23 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.168.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.170.0/23 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.172.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.172.0/23 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.172.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.173.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.74.174.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 41.75.64.0/20 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GC7-AFRINIC [GVA Congo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 41.76.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42235] Prefix was owned by ORG-IL21-AFRINIC [IS - Internet Solutions Mozambique, Limitada] Route 41.76.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-HL1-AFRINIC [Hyperia Limited] Route 41.76.240.0/21 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 41.77.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42235] Prefix was owned by ORG-IL21-AFRINIC [IS - Internet Solutions Mozambique, Limitada] Route 41.77.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36666] Prefix was owned by ORG-GC6-AFRINIC [Genious Communications] Route 41.77.128.0/21 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.128.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.129.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.130.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.131.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.132.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.133.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.134.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.135.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.77.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 41.77.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 41.77.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.78.8.0/22 [AS37661] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UoI1-AFRINIC [University of Ibadan] but owned by ORG-NRaE1-AFRINIC [Nigerian Research and Education Network Limited by Guarantee] Route 41.78.92.0/22 [AS14988] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCDS1-AFRINIC [MTN COTE D'IVOIRE S.A] but owned by ORG-BTC2-AFRINIC [Botswana Telecommunications Corporation] Route 41.78.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-MS1-AFRINIC [Microcom Sprl] Route 41.78.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38176] Prefix was owned by ORG-MS1-AFRINIC [Microcom Sprl] Route 41.79.108.0/22 [AS37315] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GA3-AFRINIC [Go2Cloud] but owned by ORG-CA6-AFRINIC [Cipherwave] Route 41.79.120.0/22 [AS327786] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZSS1-AFRINIC [Zain South Sudan] but owned by ORG-TA39-AFRINIC [4G Telecom] Route 41.79.132.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.79.134.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.79.160.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PC1-AFRINIC [Platformity CC] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 41.79.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132692] Prefix was owned by ORG-FiBS1-AFRINIC [First in Business Solutions] Route 41.79.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-ZCL1-AFRINIC [Zee Communications Ltd] Route 41.79.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCML1-AFRINIC [Gateway Communications Mozambique, Limidata] Route 41.79.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCML1-AFRINIC [Gateway Communications Mozambique, Limidata] Route 41.79.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.79.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.79.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.82.0.0/15 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.162.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.164.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.166.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.170.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.176.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.180.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.182.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.210.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.82.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.96.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.224.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.83.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.84.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.84.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.84.136.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.84.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.84.148.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.84.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.84.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.84.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.85.4.0/24 [AS328418] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FN1-AFRINIC [Frogfoot Networks] but owned by ORG-OTC1-AFRINIC [Olena Trading cc] Route 41.85.64.0/24 [AS328418] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FN1-AFRINIC [Frogfoot Networks] but owned by ORG-OTC1-AFRINIC [Olena Trading cc] Route 41.85.204.0/22 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 41.85.204.0/23 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 41.85.204.0/24 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 41.85.206.0/24 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 41.85.207.0/24 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 41.86.160.0/19 [AS22354] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.87.176.0/21 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BBI1-AFRINIC [Broadband Botswana Internet] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 41.87.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-BBI1-AFRINIC [Broadband Botswana Internet] Route 41.92.201.0/24 [AS36955] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NCS1-AFRINIC [NEWTELNET CAMEROUN SAS] but owned by ORG-MT1-AFRINIC [Matrix Telecoms SA] Route 41.92.216.0/22 [AS36955] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NCS1-AFRINIC [NEWTELNET CAMEROUN SAS] but owned by ORG-MT1-AFRINIC [Matrix Telecoms SA] Route 41.92.224.0/24 [AS36955] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NCS1-AFRINIC [NEWTELNET CAMEROUN SAS] but owned by ORG-MT1-AFRINIC [Matrix Telecoms SA] Route 41.92.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-NCS1-AFRINIC [NEWTELNET CAMEROUN SAS] Route 41.92.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-NCS1-AFRINIC [NEWTELNET CAMEROUN SAS] Route 41.92.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-NCS1-AFRINIC [NEWTELNET CAMEROUN SAS] Route 41.136.0.0/16 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.0.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.64.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.128.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.192.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.192.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.194.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.195.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.196.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.198.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.200.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.201.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.202.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.136.240.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.137.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198949] Prefix was owned by ORG-MC5-AFRINIC [Wana Corporate] Route 41.137.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198949] Prefix was owned by ORG-MC5-AFRINIC [Wana Corporate] Route 41.138.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-VCL3-AFRINIC [Visafone Communications Limited] Route 41.138.245.0/24 [AS328306] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IAL1-AFRINIC [INTERSAT AFRICA LTD] but owned by ORG-ACSA1-AFRINIC [Avanti Communications South Africa (Pty) Ltd] Route 41.138.246.0/24 [AS328306] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IAL1-AFRINIC [INTERSAT AFRICA LTD] but owned by ORG-ACSA1-AFRINIC [Avanti Communications South Africa (Pty) Ltd] Route 41.139.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.48.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.50.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.54.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.139.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.149.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65656] Prefix was owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 41.149.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65656] Prefix was owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 41.160.0.0/12 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.160.0.0/14 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.160.38.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.160.88.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.160.163.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.160.165.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.160.244.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.164.0.0/15 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.164.37.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.164.129.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.164.136.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.164.139.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.164.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.165.67.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.168.0.0/17 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.168.128.0/17 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.168.130.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.168.135.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.169.23.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.169.55.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.169.80.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.170.2.0/24 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.170.38.0/24 [AS328312] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-DTSA1-AFRINIC [Deloitte & Touche South Africa] Route 41.173.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.28.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.29.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.30.0/23 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.32.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.33.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.34.0/23 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.37.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.48.0/21 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.57.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.58.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.59.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.194.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.196.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.204.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.208.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.208.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.210.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.212.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.214.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.216.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.216.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.220.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.232.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.236.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.173.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.173.248.0/22 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.252.0/22 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.173.255.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.174.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.64.0/19 [AS37485] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-DCaS1-AFRINIC [Data Control and Systems] Route 41.174.97.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.98.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.105.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.106.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.110.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.120.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65510] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65510] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.180.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.182.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.185.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.186.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.174.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.174.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.64.0/20 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.80.0/20 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.96.0/19 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.144.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.147.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.154.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.186.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.200.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 41.175.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.222.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.240.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.175.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.176.32.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.48.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.62.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.64.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.66.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.104.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.112.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.120.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.124.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.128.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.132.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.133.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.134.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.135.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.136.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.137.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.138.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.139.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.140.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.143.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.146.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.149.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.156.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.159.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.161.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.166.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.168.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.176.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.184.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.192.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.224.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.240.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.248.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.252.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.176.255.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.188.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198381] Prefix was owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 41.189.64.0/19 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EBS1-AFRINIC [Ensync Business Solutions (PTY)Ltd] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 41.190.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.190.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.191.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-iAZL1-AFRINIC [iSAT Africa Zambia Ltd] Route 41.191.118.0/24 [AS328724] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-iAZL1-AFRINIC [iSAT Africa Zambia Ltd] but owned by ORG-IAKL1-AFRINIC [ISAT AFRICA KENYA LTD] Route 41.191.224.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.193.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-DPBO1-AFRINIC [Vox Telecom Ltd] Route 41.193.240.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-DPBO1-AFRINIC [Vox Telecom Ltd] Route 41.193.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-DPBO1-AFRINIC [Vox Telecom Ltd] Route 41.194.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-IA39-AFRINIC [Intelsat] Route 41.194.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-IA39-AFRINIC [Intelsat] Route 41.194.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-IA39-AFRINIC [Intelsat] Route 41.194.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-IA39-AFRINIC [Intelsat] Route 41.198.10.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 41.198.11.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 41.198.12.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 41.198.13.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 41.198.64.0/20 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 41.198.97.0/24 [AS328306] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-ACSA1-AFRINIC [Avanti Communications South Africa (Pty) Ltd] Route 41.198.240.0/20 [AS328306] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-ACSA1-AFRINIC [Avanti Communications South Africa (Pty) Ltd] Route 41.198.240.0/22 [AS328306] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-ACSA1-AFRINIC [Avanti Communications South Africa (Pty) Ltd] Route 41.198.244.0/22 [AS328306] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-ACSA1-AFRINIC [Avanti Communications South Africa (Pty) Ltd] Route 41.199.0.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.16.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.24.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.32.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.33.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.34.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.36.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.38.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.52.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.53.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.54.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.56.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.60.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.97.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.98.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.102.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.104.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.105.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.106.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.108.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.109.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.110.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.111.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.120.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.124.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.128.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.144.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.160.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.176.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.184.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.192.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.196.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.248.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.252.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.199.253.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 41.200.0.0/18 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.0.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.1.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.2.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.3.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.4.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.5.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.6.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.7.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.8.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.9.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.10.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.11.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.12.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.13.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.14.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.15.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.16.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.17.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.18.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.19.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.20.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.21.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.22.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.23.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.24.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.25.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.26.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.27.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.28.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.29.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.30.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.31.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.32.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.33.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.34.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.35.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.36.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.37.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.38.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.39.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.40.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.41.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.42.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.43.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.44.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.45.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.46.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.47.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.48.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.49.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.50.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.51.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.52.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.53.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.54.0/24 [AS327931] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-OTA3-AFRINIC [Optimum Telecom Algeria] Route 41.200.64.0/18 [AS33779] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-WTA1-AFRINIC [Wataniya Telecom Algerie] Route 41.200.64.0/20 [AS33779] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TA23-AFRINIC [Telecom Algeria] but owned by ORG-WTA1-AFRINIC [Wataniya Telecom Algerie] Route 41.203.107.0/24 [AS36993] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-FCMB1-AFRINIC [First City Monument Bank, PLC] Route 41.203.110.0/24 [AS37025] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-BP1-AFRINIC [BANKPHB PLC] Route 41.203.111.0/24 [AS37025] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-BP1-AFRINIC [BANKPHB PLC] Route 41.203.112.0/24 [AS37001] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-GTBP1-AFRINIC [Guaranty Trust Bank Plc] Route 41.203.113.0/24 [AS37056] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-ZBP1-AFRINIC [Zenith Bank PLC] Route 41.203.114.0/24 [AS37056] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-ZBP1-AFRINIC [Zenith Bank PLC] Route 41.203.115.0/24 [AS37104] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-SIBP1-AFRINIC [STANBIC IBTC BANK PLC] Route 41.203.116.0/24 [AS37104] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-SIBP1-AFRINIC [STANBIC IBTC BANK PLC] Route 41.203.118.0/24 [AS37269] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-ICSL1-AFRINIC [Information Connectivity Solutions Limited] Route 41.203.119.0/24 [AS37269] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-ICSL1-AFRINIC [Information Connectivity Solutions Limited] Route 41.203.124.0/24 [AS37056] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-ZBP1-AFRINIC [Zenith Bank PLC] Route 41.204.190.0/24 [AS327945] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KEN1-AFRINIC [Kenya Education Network] but owned by ORG-ILRI1-AFRINIC [International Livestock Research Institute] Route 41.205.100.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 41.205.101.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 41.205.103.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 41.205.104.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 41.206.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.206.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.206.48.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.206.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.206.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6453] Prefix was owned by ORG-TCU1-AFRINIC [TATA Communications] Route 41.206.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6453] Prefix was owned by ORG-TCU1-AFRINIC [TATA Communications] Route 41.206.184.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6453] Prefix was owned by ORG-TCU1-AFRINIC [TATA Communications] Route 41.206.188.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6453] Prefix was owned by ORG-TCU1-AFRINIC [TATA Communications] Route 41.206.204.0/24 [AS328418] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FN1-AFRINIC [Frogfoot Networks] but owned by ORG-OTC1-AFRINIC [Olena Trading cc] Route 41.206.205.0/24 [AS328418] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FN1-AFRINIC [Frogfoot Networks] but owned by ORG-OTC1-AFRINIC [Olena Trading cc] Route 41.207.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.170.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 41.207.232.0/22 [AS37100] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PA13-AFRINIC [Pamoja, Ltd] but owned by ORG-SL75-AFRINIC [SEACOM Limited] Route 41.207.252.0/22 [AS37282] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCCL1-AFRINIC [MainOne Cable Company (Ghana) Ltd] but owned by ORG-MCC1-AFRINIC [Mainone Cable Company] Route 41.208.64.0/18 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.64.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.65.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.66.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.67.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.68.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.69.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.70.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.71.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.72.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.73.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.74.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.75.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.76.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.77.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.78.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.79.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.80.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.81.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.82.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.83.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.84.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.85.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.86.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.88.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.89.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.90.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.91.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.92.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.93.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.94.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.95.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.96.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.97.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.98.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.99.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.100.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.101.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.102.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.103.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.104.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.105.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.106.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.107.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.108.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.109.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.110.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.111.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.112.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.113.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.114.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.115.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.117.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.118.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.119.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.120.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.121.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.122.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.123.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.124.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.125.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.126.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.127.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.208.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.140.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.208.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.209.3.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.5.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.8.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.8.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.9.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.10.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.12.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.14.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.15.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.16.0/20 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.16.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.17.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.18.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.19.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.21.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.22.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.23.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.24.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.24.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.28.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.32.0/20 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.32.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.39.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.40.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.43.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.48.0/20 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.48.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.49.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.50.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.51.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.53.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.56.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.57.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.209.60.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 41.211.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.211.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35091] Prefix was owned by ORG-TIL1-AFRINIC [Teledata ICT Ltd] Route 41.212.128.0/17 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.212.128.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.212.128.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.212.143.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.212.168.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.212.212.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.214.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.48.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.214.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 41.215.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.215.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 41.215.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 41.215.244.0/24 [AS329267] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KTL2-AFRINIC [KKON Technologies Ltd] but owned by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] Route 41.215.248.0/22 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.215.249.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.215.250.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.96.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.97.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.98.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.99.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.100.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.101.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.102.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.103.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.104.0/21 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.112.0/21 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.120.0/23 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.122.0/23 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.126.0/23 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.216.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.216.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212738] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139989] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139989] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139989] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213035] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41745] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139989] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211407] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212027] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211138] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211138] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211407] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211407] Prefix was owned by ORG-FL4-AFRINIC [FASTHOSTING (PTY) LTD] Route 41.216.208.0/21 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 41.217.194.0/23 [AS36937] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UN1-AFRINIC [Umoya Networks] but owned by ORG-NPL2-AFRINIC [Liquid Telecommunications South Africa (Pty) Ltd] Route 41.220.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 41.220.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 41.220.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.220.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 41.220.200.0/24 [AS30619] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCS4-AFRINIC [Mocambique Celular, SARL] but owned by ORG-TMTS1-AFRINIC [TMCEL - Mo??ambique Telecom, SA] Route 41.220.201.0/24 [AS30619] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCS4-AFRINIC [Mocambique Celular, SARL] but owned by ORG-TMTS1-AFRINIC [TMCEL - Mo??ambique Telecom, SA] Route 41.220.208.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.210.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.212.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29032] Prefix was owned by ORG-DL2-AFRINIC [DATANET.COM LLC] Route 41.220.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.220.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.220.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.220.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.220.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.220.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.221.35.0/24 [AS16907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 41.221.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.221.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.221.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.221.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40123] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.221.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.221.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.221.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 41.222.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 41.222.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64512] Prefix was owned by ORG-EM2-AFRINIC [Ethekwini Municipality] Route 41.223.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 41.223.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 41.223.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 41.223.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-MS1-AFRINIC [Microcom Sprl] Route 41.223.144.0/24 [AS37001] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-GTBP1-AFRINIC [Guaranty Trust Bank Plc] Route 41.223.146.0/24 [AS36979] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-FBoN1-AFRINIC [First Bank of NG PLC] Route 41.223.147.0/24 [AS36993] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL19-AFRINIC [IPARTNERS LIMITED] but owned by ORG-FCMB1-AFRINIC [First City Monument Bank, PLC] Route 41.223.152.0/22 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.223.152.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.223.153.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.223.154.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.223.155.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 41.223.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-ZCL1-AFRINIC [Zee Communications Ltd] Route 41.223.195.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DVLt3-AFRINIC [Dapit Ventures (PTY) Ltd t/a GCSat Botswana] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 41.223.220.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MFDC1-AFRINIC [Mauritius Freeport Development Company Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 41.223.224.0/22 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.223.225.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.223.227.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 41.223.236.0/22 [AS36947] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IS33-AFRINIC [ISSALNET SARL] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 41.223.240.0/24 [AS30995] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CBoE1-AFRINIC [Commercial International Bank of Egypt] but owned by ORG-RT2-AFRINIC [Vodafone Data] Route 41.223.241.0/24 [AS30995] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CBoE1-AFRINIC [Commercial International Bank of Egypt] but owned by ORG-RT2-AFRINIC [Vodafone Data] Route 41.223.242.0/24 [AS30995] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CBoE1-AFRINIC [Commercial International Bank of Egypt] but owned by ORG-RT2-AFRINIC [Vodafone Data] Route 41.223.243.0/24 [AS30995] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CBoE1-AFRINIC [Commercial International Bank of Egypt] but owned by ORG-RT2-AFRINIC [Vodafone Data] Route 41.223.244.0/22 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 41.223.244.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 41.223.245.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 41.223.246.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 41.223.247.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 41.224.0.0/13 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.224.0.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.0.0/20 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.4.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.6.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.8.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.12.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.13.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.16.0/20 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.32.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.33.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.35.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.36.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.40.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.42.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.44.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.48.0/20 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.62.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.64.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.64.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.96.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.128.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.128.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.192.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.192.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.221.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.224.224.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.225.0.0/16 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.225.128.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.226.0.0/16 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.0.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.4.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.6.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.7.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.8.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.8.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.9.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.11.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.12.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.13.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.14.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.15.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.16.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.17.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.18.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.20.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.21.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.22.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.23.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.24.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.25.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.27.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.28.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.32.0/21 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.40.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.48.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.49.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.50.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.52.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.60.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.64.0/19 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.96.0/19 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.144.0/20 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.160.0/21 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.168.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.172.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.176.0/21 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.192.0/19 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.224.0/20 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.240.0/21 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.226.248.0/21 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.227.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.227.4.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.16.0/20 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.32.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.64.0/19 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.227.64.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.227.80.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.227.96.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.128.0/20 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.144.0/20 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.160.0/20 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.176.0/21 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.184.0/21 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.192.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.227.224.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 41.228.0.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.0.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.2.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.4.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.4.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.6.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.8.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.8.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.10.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.12.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.12.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.14.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.16.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.16.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.18.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.20.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.20.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.22.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.24.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.24.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.26.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.32.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.32.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.34.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.36.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.36.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.37.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.38.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.38.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.39.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.40.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.41.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.44.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.44.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.46.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.48.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.52.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.52.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.54.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.56.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.56.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.58.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.64.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.228.64.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.228.96.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.228.128.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.228.128.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.228.160.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.228.192.0/19 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.192.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.208.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.224.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.224.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.226.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.228.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.228.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.229.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.230.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.230.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.231.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.232.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.232.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.236.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.240.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.240.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.228.248.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.229.0.0/16 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.0.0/23 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.2.0/23 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.6.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.7.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.15.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.22.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.23.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.25.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.29.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.35.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.36.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.52.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.54.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.58.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.64.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.68.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.69.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.70.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.71.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.72.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.73.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.78.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.79.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.80.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.82.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.83.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.84.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.89.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.90.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.91.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.96.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.104.0/23 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.106.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.107.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.109.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.111.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.116.0/23 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.117.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.118.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.119.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.120.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.121.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.122.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.123.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.124.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.125.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.126.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.127.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.138.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.226.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.228.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.230.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.232.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.233.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.236.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.237.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.240.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.241.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.244.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.246.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.229.250.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 41.230.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.230.0.0/17 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.0.0/19 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.32.0/20 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.48.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.49.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.50.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.52.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.56.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.60.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.64.0/19 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.128.0/18 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.192.0/20 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.230.208.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.230.208.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.230.210.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.230.212.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.230.216.0/21 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.230.216.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.230.220.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.230.224.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.230.224.0/20 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.230.240.0/20 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.231.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.3.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.5.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.6.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 41.231.7.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 41.231.8.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.9.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.12.0/22 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.12.0/23 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.14.0/23 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.16.0/23 [AS327969] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-ATB3-AFRINIC [Arab Tunisian Bank] Route 41.231.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.23.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.30.0/23 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.231.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.45.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.46.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.47.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.54.0/24 [AS329268] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SS7-AFRINIC [STE SAFOZI] Route 41.231.56.0/21 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 41.231.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.82.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.84.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 41.231.88.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 41.231.103.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.104.0/22 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.108.0/22 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.108.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.109.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.110.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.111.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.122.0/24 [AS329268] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SS7-AFRINIC [STE SAFOZI] Route 41.231.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.180.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.186.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.206.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.212.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.216.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.218.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.224.0/22 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.228.0/22 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.232.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.231.232.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.231.234.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 41.231.236.0/22 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.236.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.237.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.238.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.239.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.240.0/22 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 41.231.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.231.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 41.232.0.0/13 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.232.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.233.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.64.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.234.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.235.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.64.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.230.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.236.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.237.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.238.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.239.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 41.242.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49902] Prefix was owned by ORG-SRdR1-AFRINIC [Societe Reunionnaise du Radiotelephone] Route 41.243.12.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CD1-AFRINIC [CELTEL DRC] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 41.243.13.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CD1-AFRINIC [CELTEL DRC] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 41.243.63.0/24 [AS36926] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CD1-AFRINIC [CELTEL DRC] but owned by ORG-CKL1-AFRINIC [Airtel Networks Kenya Limited] Route 41.252.0.0/14 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.252.96.0/20 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.16.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.38.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.49.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.50.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.53.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.61.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.64.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.65.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.66.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.67.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.68.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.69.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.70.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.71.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.73.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.74.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.75.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.76.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.77.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.81.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.82.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.83.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.84.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.85.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.86.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.87.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 41.254.88.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 45.192.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213690] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133180] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139871] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262191] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215391] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153347] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.22.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132537] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132537] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132537] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.116.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.118.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.128.0/19 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.192.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134824] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401254] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398478] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.246.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.248.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS33182] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.192.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.193.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.193.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.193.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.193.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.193.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.193.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214049] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273222] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.20.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27947] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS52925] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.46.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269843] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137184] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134963] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134963] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134963] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134963] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147019] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147019] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147019] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147019] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS204741] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.66.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.194.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141718] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134824] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45996] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45996] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.112.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.114.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273986] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207251] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273824] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.208.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.194.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4809] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272854] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272854] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS274089] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211871] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132585] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400046] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137962] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45996] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211567] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60446] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS204741] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138168] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.82.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273824] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273824] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273824] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS52468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.106.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS274089] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27947] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135405] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215618] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26617] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141735] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.148.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140883] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140925] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213799] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS39600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.202.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26617] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26617] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138910] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138910] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.244.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.246.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59134] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133115] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.195.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.14.0/23 [AS327790] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 45.196.14.0/24 [AS327790] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 45.196.15.0/24 [AS327790] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 45.196.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.20.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45102] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.30.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.196.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133073] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35107] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.206.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS10103] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.216.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.218.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401615] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401615] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401615] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.220.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.234.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.236.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.238.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401615] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152599] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140224] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140224] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140224] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.196.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.0.0/18 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.16.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.18.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.19.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14315] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150000] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150000] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134365] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.160.0/19 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.160.0/21 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.172.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.173.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.174.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.175.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.176.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.177.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.178.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.179.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.180.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.184.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.188.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.197.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS264628] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS264628] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.224.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.197.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141109] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60446] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149940] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140641] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140641] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215691] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215691] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272018] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272018] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272018] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS1100] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152686] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35086] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.186.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152686] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.232.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141109] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141109] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141109] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.238.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132566] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132566] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132566] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132566] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.240.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132566] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132566] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.244.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132566] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140401] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211188] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.198.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140659] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140659] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54252] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32848] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32848] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27947] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45102] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135405] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133012] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138985] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.199.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149641] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.80.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.82.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.84.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS148994] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS148994] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS148994] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS148994] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS148994] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.96.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.104.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.106.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151206] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151206] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151206] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131618] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60609] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60609] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60609] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60609] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398478] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.200.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2914] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.128.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.132.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139226] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139226] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.164.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.166.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.168.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.170.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.188.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.190.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.208.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131178] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.218.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.220.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.222.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.224.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.228.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.230.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.240.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.244.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.246.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.248.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.201.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.42.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.44.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142629] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2914] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401366] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.100.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214025] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.194.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14315] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152711] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.216.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.248.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.202.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.0.0/18 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 45.203.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.166.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.196.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.222.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.203.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132825] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS216047] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137510] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS154177] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.204.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.24.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.80.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.96.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.110.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.152.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.160.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.170.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.205.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55154] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.44.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.62.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.206.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42831] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.34.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44509] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.136.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.138.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.140.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.142.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.152.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.154.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.156.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.158.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.164.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137184] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38638] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212667] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212667] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.200.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.202.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.204.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.206.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.208.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.218.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.244.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.246.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.207.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 45.215.250.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZP1-AFRINIC [Zain Zambia PLC] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 45.221.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS715] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 45.221.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS715] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 45.221.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS34927] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 45.221.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54339] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 45.221.72.0/21 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.73.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.74.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.75.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.76.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.77.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.78.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.79.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 45.221.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS967] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS967] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS967] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS967] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55933] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.119.0/24 [AS328543] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] but owned by ORG-SNCL1-AFRINIC [Sun Network Company Limited] Route 45.221.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138968] Prefix was owned by ORG-BE1-AFRINIC [BLUEGATE EXCHANGE] Route 45.221.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-STS2-AFRINIC [SUD TELECOM SOLUTIONS] Route 45.222.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198394] Prefix was owned by ORG-ZNL1-AFRINIC [Zeta-web Nigeria Limited] Route 45.222.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198504] Prefix was owned by ORG-ZNL1-AFRINIC [Zeta-web Nigeria Limited] Route 45.222.192.0/18 [AS37282] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCCL1-AFRINIC [MainOne Cable Company (Ghana) Ltd] but owned by ORG-MCC1-AFRINIC [Mainone Cable Company] Route 62.8.74.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 62.8.83.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 62.8.85.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 62.61.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49902] Prefix was owned by ORG-SRdR1-AFRINIC [Societe Reunionnaise du Radiotelephone] Route 62.114.0.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.24.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.48.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.49.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.50.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.51.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.52.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.56.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.72.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.96.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.104.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.112.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.120.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.121.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.122.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.123.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.126.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.128.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.160.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.192.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.208.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.224.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.114.252.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.0.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.10.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.23.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.29.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.33.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.34.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.37.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.40.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.48.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.48.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.56.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.66.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.72.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.77.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.80.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.89.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.96.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.112.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.124.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.134.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.136.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.152.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.166.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.180.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.184.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.192.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.204.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.212.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.213.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.216.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.236.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.240.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.139.255.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.64.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.73.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.79.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.87.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.89.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.93.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.96.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.140.127.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.64.0/18 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.66.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.67.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.68.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.69.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.70.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.72.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.73.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.74.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.75.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.76.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.77.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.79.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.81.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.82.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.84.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.85.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.86.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.88.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.89.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.91.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.92.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.93.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.94.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.95.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.96.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.96.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.97.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.98.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.99.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.100.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.101.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.102.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.103.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.104.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.105.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.106.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.107.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.108.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.109.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.110.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.111.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.114.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.116.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.117.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.118.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.120.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.121.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.193.123.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 62.240.32.0/19 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 62.240.36.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 62.240.57.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 62.240.63.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTaT1-AFRINIC [Libyan Telecom and Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 66.18.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-IL12-AFRINIC [Sentech SOC Ltd] Route 66.251.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53356] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53356] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53356] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53356] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53356] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53356] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 66.251.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] Route 80.72.96.0/20 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ACL2-AFRINIC [Afsat Communications Ltd] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 80.75.160.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.161.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.164.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.165.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.166.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.167.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.168.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.169.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.171.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.172.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.173.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.180.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.188.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EA19-AFRINIC [EgyNet] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.75.189.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EA19-AFRINIC [EgyNet] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 80.87.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-GTCL1-AFRINIC [Ghana Telecommunications Company Limited] Route 80.88.3.0/24 [AS37287] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CECP1-AFRINIC [Copperbelt Energy Corporation Plc] but owned by ORG-ZZP1-AFRINIC [Zain Zambia PLC] Route 80.240.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 80.240.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 80.240.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 80.240.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 80.250.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7155] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7155] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7155] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 80.250.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 81.10.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 81.10.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 81.10.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 81.10.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 81.10.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 82.129.208.0/24 [AS328553] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RT2-AFRINIC [Vodafone Data] but owned by ORG-BMS1-AFRINIC [Bank Misr S.A.E] Route 83.143.24.0/21 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 84.36.0.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.4.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.6.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.7.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.9.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.10.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.11.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.12.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.12.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.13.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.14.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.15.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.16.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.17.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.18.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.20.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.20.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.21.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.22.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.23.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.24.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.25.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.26.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.27.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.28.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.31.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.32.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.34.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.35.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.36.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.36.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.37.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.38.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.38.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.39.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.40.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.41.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.42.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.43.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.47.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.48.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.49.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.50.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.53.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.54.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.55.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.56.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.56.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.58.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.59.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.62.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.63.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.64.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.64.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.65.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.66.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.67.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.70.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.72.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.74.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.79.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.80.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.81.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.82.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.83.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.84.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.85.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.86.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.87.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.88.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.88.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.89.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.90.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.91.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.92.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.93.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.94.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.94.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.95.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.96.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.97.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.98.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.99.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.100.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.101.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.102.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.103.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.104.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.105.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.106.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.107.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.108.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.109.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.110.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.110.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.113.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.114.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.115.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.116.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.117.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.118.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.119.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.120.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.120.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.121.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.128.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.129.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.130.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.131.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.132.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.133.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.136.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.160.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.163.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.164.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.166.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.167.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.169.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.170.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.176.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.190.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.192.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.195.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.199.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.209.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.212.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.213.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.219.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.220.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.224.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.227.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.228.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.229.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.230.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.232.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.233.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.235.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.236.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.239.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.241.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.242.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.36.245.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.205.96.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CS3-AFRINIC [City Stars] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.5.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.10.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.15.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.16.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.19.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.20.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.30.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.66.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.67.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.72.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.74.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.75.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.80.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.94.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.95.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.113.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.117.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.118.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.125.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 84.233.126.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 87.255.96.0/19 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ACL2-AFRINIC [Afsat Communications Ltd] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 102.0.123.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CKL1-AFRINIC [Airtel Networks Kenya Limited] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 102.22.64.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.65.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.66.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.70.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.72.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.73.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.74.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.75.0/24 [AS327907] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL1-AFRINIC [VOD Communications (Pty) Ltd] but owned by ORG-PWL1-AFRINIC [Session Telecoms(PTY) Ltd] Route 102.22.128.0/18 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GRL1-AFRINIC [GVA Rwanda Ltd] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.22.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64519] Prefix was owned by ORG-SP4-AFRINIC [Surf4Life Pty (LTD)] Route 102.22.244.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64519] Prefix was owned by ORG-SP4-AFRINIC [Surf4Life Pty (LTD)] Route 102.23.0.0/18 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GBF1-AFRINIC [GVA Burkina Faso] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.23.176.0/24 [AS328137] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DADT2-AFRINIC [D and D Tactical (Pty) Ltd] but owned by ORG-WSCL1-AFRINIC [Web Squad Connect (Pty) Ltd] Route 102.23.177.0/24 [AS328137] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DADT2-AFRINIC [D and D Tactical (Pty) Ltd] but owned by ORG-WSCL1-AFRINIC [Web Squad Connect (Pty) Ltd] Route 102.23.178.0/24 [AS328137] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DADT2-AFRINIC [D and D Tactical (Pty) Ltd] but owned by ORG-WSCL1-AFRINIC [Web Squad Connect (Pty) Ltd] Route 102.23.182.0/24 [AS328137] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DADT2-AFRINIC [D and D Tactical (Pty) Ltd] but owned by ORG-WSCL1-AFRINIC [Web Squad Connect (Pty) Ltd] Route 102.23.183.0/24 [AS328473] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DADT2-AFRINIC [D and D Tactical (Pty) Ltd] but owned by ORG-BBL1-AFRINIC [Be Broadband (PTY) LTD] Route 102.23.207.0/24 [AS328748] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TTC2-AFRINIC [TOUCHNET TELECOMMUNICATIONS CC] but owned by ORG-ASPL1-AFRINIC [Agile Solutions Provider (PTY) LTD] Route 102.36.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS43260] Prefix was owned by ORG-NSL5-AFRINIC [NetIT Solutions LTD] Route 102.36.196.0/22 [AS328583] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WB2-AFRINIC [Wiselink Broadband] but owned by ORG-CTC2-AFRINIC [CRAZYWEB TECH (PTY) LTD] Route 102.36.196.0/23 [AS328583] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WB2-AFRINIC [Wiselink Broadband] but owned by ORG-CTC2-AFRINIC [CRAZYWEB TECH (PTY) LTD] Route 102.36.196.0/24 [AS328583] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WB2-AFRINIC [Wiselink Broadband] but owned by ORG-CTC2-AFRINIC [CRAZYWEB TECH (PTY) LTD] Route 102.36.197.0/24 [AS328583] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WB2-AFRINIC [Wiselink Broadband] but owned by ORG-CTC2-AFRINIC [CRAZYWEB TECH (PTY) LTD] Route 102.36.198.0/23 [AS328583] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WB2-AFRINIC [Wiselink Broadband] but owned by ORG-CTC2-AFRINIC [CRAZYWEB TECH (PTY) LTD] Route 102.36.198.0/24 [AS328583] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WB2-AFRINIC [Wiselink Broadband] but owned by ORG-CTC2-AFRINIC [CRAZYWEB TECH (PTY) LTD] Route 102.36.199.0/24 [AS328583] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WB2-AFRINIC [Wiselink Broadband] but owned by ORG-CTC2-AFRINIC [CRAZYWEB TECH (PTY) LTD] Route 102.36.216.0/21 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.36.218.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.36.219.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.36.220.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.36.221.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.36.222.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.36.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] Route 102.37.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-ML12-AFRINIC [Microsoft (S.A.) (Proprietary) Limited] Route 102.37.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-ML12-AFRINIC [Microsoft (S.A.) (Proprietary) Limited] Route 102.37.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-ML12-AFRINIC [Microsoft (S.A.) (Proprietary) Limited] Route 102.38.60.0/22 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCL5-AFRINIC [MAXINET COMMUNICATIONS (PTY) LTD] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 102.38.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS52000] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.38.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-TSL10-AFRINIC [Technology Software Limited] Route 102.40.0.0/13 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.40.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.41.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.42.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.43.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.44.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.45.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.46.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.47.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 102.64.122.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36352] Prefix was owned by ORG-FSPL1-AFRINIC [FAST SERVERS PTY LIMITED] Route 102.64.128.0/17 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GT7-AFRINIC [GVA Togo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.65.32.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WANL1-AFRINIC [Web Africa Networks (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 102.65.33.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WANL1-AFRINIC [Web Africa Networks (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 102.65.34.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WANL1-AFRINIC [Web Africa Networks (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 102.65.35.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WANL1-AFRINIC [Web Africa Networks (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 102.67.12.0/24 [AS329267] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KTL2-AFRINIC [KKON Technologies Ltd] but owned by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] Route 102.67.21.0/24 [AS329267] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KTL2-AFRINIC [KKON Technologies Ltd] but owned by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] Route 102.67.164.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36236] Prefix was owned by ORG-NZ1-AFRINIC [NETACTUATE ZA] Route 102.67.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36236] Prefix was owned by ORG-NZ1-AFRINIC [NETACTUATE ZA] Route 102.67.166.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36236] Prefix was owned by ORG-NZ1-AFRINIC [NETACTUATE ZA] Route 102.67.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36236] Prefix was owned by ORG-NZ1-AFRINIC [NETACTUATE ZA] Route 102.67.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36236] Prefix was owned by ORG-NZ1-AFRINIC [NETACTUATE ZA] Route 102.67.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-RTNL1-AFRINIC [Radical Technology Network Limited] Route 102.68.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS39600] Prefix was owned by ORG-SL82-AFRINIC [Swazisat (Proprietary) Limited] Route 102.68.72.0/22 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TCSP1-AFRINIC [The Computer Shop Plett] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 102.68.128.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.68.129.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.68.131.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.68.132.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.68.133.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.68.134.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.68.135.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.69.32.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.36.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.40.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.44.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.48.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.52.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.56.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.60.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.68.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.72.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.72.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.74.0/23 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.80.0/20 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.80.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.84.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.88.0/21 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LICF1-AFRINIC [Libyan International Company for Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.69.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-MT4-AFRINIC [M'Data Telecom] Route 102.69.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-MT4-AFRINIC [M'Data Telecom] Route 102.69.236.0/23 [AS37314] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CL16-AFRINIC [Cellfind (Pty) Ltd] but owned by ORG-SI4-AFRINIC [Inq Digital South Africa (Pty) Ltd] Route 102.69.237.0/24 [AS37314] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CL16-AFRINIC [Cellfind (Pty) Ltd] but owned by ORG-SI4-AFRINIC [Inq Digital South Africa (Pty) Ltd] Route 102.88.0.0/13 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.88.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.89.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.90.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.91.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.92.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.92.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.92.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.92.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.92.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.92.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.92.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.93.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.93.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.93.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.93.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 102.128.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DHSL1-AFRINIC [Dedicated Hosting Solutions Limited] Route 102.128.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DHSL1-AFRINIC [Dedicated Hosting Solutions Limited] Route 102.128.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35758] Prefix was owned by ORG-DHSL1-AFRINIC [Dedicated Hosting Solutions Limited] Route 102.128.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205659] Prefix was owned by ORG-DHSL1-AFRINIC [Dedicated Hosting Solutions Limited] Route 102.128.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18417] Prefix was owned by ORG-WL8-AFRINIC [Wirelexx (Pty) Ltd] Route 102.129.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.129.0/24 [AS37468] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] but owned by ORG-AC4-AFRINIC [Angola Cables] Route 102.129.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53340] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200017] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211192] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135402] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212609] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54339] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.165.0/24 [AS329184] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] but owned by ORG-CTML1-AFRINIC [Host Africa (Pty) Ltd] Route 102.129.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4637] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62390] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133337] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7018] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32181] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32181] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58061] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400810] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62390] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212335] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137962] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62390] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20001] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212384] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397373] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS208949] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60949] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212384] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200017] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS199959] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211192] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26042] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36352] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6315] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6315] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58061] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20648] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138156] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26042] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20001] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.245.0/24 [AS327813] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] but owned by ORG-CTML1-AFRINIC [Host Africa (Pty) Ltd] Route 102.129.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215224] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11170] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209181] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.129.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.130.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35487] Prefix was owned by ORG-XL1-AFRINIC [xTom Limited] Route 102.130.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35487] Prefix was owned by ORG-XL1-AFRINIC [xTom Limited] Route 102.130.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS969] Prefix was owned by ORG-XL1-AFRINIC [xTom Limited] Route 102.130.96.0/24 [AS327808] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SAA1-AFRINIC [South African Airways] but owned by ORG-TTL2-AFRINIC [TESUCO TELECOMMUNICATIONS (PTY) LTD] Route 102.130.224.0/21 [AS37282] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCD1-AFRINIC [MainOne COTE D'IVOIRE] but owned by ORG-MCC1-AFRINIC [Mainone Cable Company] Route 102.130.232.0/22 [AS21271] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DS6-AFRINIC [DATATECH SARL] but owned by ORG-SoMT1-AFRINIC [Society of Mali's Telecommunications (SOTELMA)] Route 102.130.254.0/23 [AS37474] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SIA2-AFRINIC [Sudanese Internet Association] but owned by ORG-IS32-AFRINIC [ISPA SA] Route 102.131.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65002] Prefix was owned by ORG-VO1-AFRINIC [Village Operator] Route 102.131.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65002] Prefix was owned by ORG-VO1-AFRINIC [Village Operator] Route 102.132.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32934] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32934] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32934] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32934] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.132.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIc1-AFRINIC [Cool Ideas Service Provider (Pty) Ltd] Route 102.133.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-ML12-AFRINIC [Microsoft (S.A.) (Proprietary) Limited] Route 102.133.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-ML12-AFRINIC [Microsoft (S.A.) (Proprietary) Limited] Route 102.133.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-ML12-AFRINIC [Microsoft (S.A.) (Proprietary) Limited] Route 102.134.16.0/21 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WNL2-AFRINIC [WIOCC Nigeria Limited] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 102.134.22.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WNL2-AFRINIC [WIOCC Nigeria Limited] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 102.134.23.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WNL2-AFRINIC [WIOCC Nigeria Limited] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 102.134.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44592] Prefix was owned by ORG-SAS2-AFRINIC [STR AFRICA SA] Route 102.134.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55933] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138968] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138968] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138968] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.48.0/20 [AS328543] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NHD1-AFRINIC [Naafi Help Desk] but owned by ORG-SNCL1-AFRINIC [Sun Network Company Limited] Route 102.134.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400464] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400464] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400464] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400464] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS932] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS932] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS932] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS932] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS932] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55933] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138968] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138968] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138968] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-NHD1-AFRINIC [Naafi Help Desk] Route 102.134.75.0/24 [AS328317] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ISL2-AFRINIC [WANT THE FIBRE INTERNET] but owned by ORG-AGOC1-AFRINIC [AEROCOM BROADBAND SERVICES] Route 102.134.80.0/23 [AS37356] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CN3-AFRINIC [ComX Networks (PTY) LTD] but owned by ORG-SI5-AFRINIC [Huge Networks (Pty) Ltd] Route 102.134.82.0/23 [AS37356] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CN3-AFRINIC [ComX Networks (PTY) LTD] but owned by ORG-SI5-AFRINIC [Huge Networks (Pty) Ltd] Route 102.135.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS996] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS43641] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401838] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS834] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS216183] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS996] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214693] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202662] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53107] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401838] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS56913] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS996] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5065] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401838] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5065] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS56913] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 102.135.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16509] Prefix was owned by ORG-STS4-AFRINIC [STE Techplus SARL] Route 102.135.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51110] Prefix was owned by ORG-IT7-AFRINIC [IDOM Technologies] Route 102.135.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15695] Prefix was owned by ORG-EM3-AFRINIC [EXPEREO MAROC] Route 102.135.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15695] Prefix was owned by ORG-EM3-AFRINIC [EXPEREO MAROC] Route 102.135.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15695] Prefix was owned by ORG-EM3-AFRINIC [EXPEREO MAROC] Route 102.135.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15695] Prefix was owned by ORG-EM3-AFRINIC [EXPEREO MAROC] Route 102.140.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS47524] Prefix was owned by ORG-ACSA1-AFRINIC [Avanti Communications South Africa (Pty) Ltd] Route 102.140.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 102.140.208.0/23 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.141.0.0/18 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GC7-AFRINIC [GVA Congo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.141.0.0/19 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GC7-AFRINIC [GVA Congo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.141.32.0/19 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GC7-AFRINIC [GVA Congo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.142.0.0/16 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GGS1-AFRINIC [GVA Gabon SAS] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.160.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.160.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.160.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.160.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.163.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.163.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65501] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.163.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65501] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.163.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-EA20-AFRINIC [EMTEL LIMITED] Route 102.164.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-DSL5-AFRINIC [Duara Systems Limited] Route 102.164.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-DSL5-AFRINIC [Duara Systems Limited] Route 102.164.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-DSL5-AFRINIC [Duara Systems Limited] Route 102.164.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-DSL5-AFRINIC [Duara Systems Limited] Route 102.164.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-DSL5-AFRINIC [Duara Systems Limited] Route 102.164.116.0/22 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EPL2-AFRINIC [IOCO Infrastructure Services (Pty) Ltd] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 102.165.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212609] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53340] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211484] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS266400] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210870] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211192] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32181] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212669] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60949] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21840] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS270353] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58061] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20141] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS208949] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42831] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5065] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135375] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.61.0/24 [AS328617] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] but owned by ORG-SGSL1-AFRINIC [Skystar Global Solutions Limited] Route 102.165.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 102.165.112.0/23 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VL6-AFRINIC [Veritran (Private) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 102.165.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS10310] Prefix was owned by ORG-VCSA1-AFRINIC [Verizon Communications South Africa] Route 102.165.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS10310] Prefix was owned by ORG-VCSA1-AFRINIC [Verizon Communications South Africa] Route 102.176.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65000] Prefix was owned by ORG-GTCL1-AFRINIC [Ghana Telecommunications Company Limited] Route 102.176.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6774] Prefix was owned by ORG-BICS1-AFRINIC [BELGACOM INTERNATIONAL CARRIER SERVICES (MAURITIUS) LTD] Route 102.176.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6774] Prefix was owned by ORG-BICS1-AFRINIC [BELGACOM INTERNATIONAL CARRIER SERVICES (MAURITIUS) LTD] Route 102.176.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6774] Prefix was owned by ORG-BICS1-AFRINIC [BELGACOM INTERNATIONAL CARRIER SERVICES (MAURITIUS) LTD] Route 102.176.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6774] Prefix was owned by ORG-BICS1-AFRINIC [BELGACOM INTERNATIONAL CARRIER SERVICES (MAURITIUS) LTD] Route 102.176.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6774] Prefix was owned by ORG-BICS1-AFRINIC [BELGACOM INTERNATIONAL CARRIER SERVICES (MAURITIUS) LTD] Route 102.176.224.0/20 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.224.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.225.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.226.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.227.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.228.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.229.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.230.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.231.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.232.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.233.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.234.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.235.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.238.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.176.239.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 102.177.128.0/19 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.128.0/20 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.131.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.138.0/24 [AS37527] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-JTL2-AFRINIC [JIREH Technologies (PTY) Ltd.] Route 102.177.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS34549] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.141.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.144.0/20 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.144.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.145.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.146.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.148.0/24 [AS327794] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-CAL1-AFRINIC [Clear Access (Pty) Ltd] Route 102.177.150.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.152.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.153.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.154.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.177.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211826] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140867] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141718] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200113] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29684] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29684] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.177.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CWL1-AFRINIC [Crystal Web (Pty) Ltd] Route 102.204.124.0/24 [AS37451] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TDC1-AFRINIC [TELECOMMUNICATION DU CONGO] but owned by ORG-CT6-AFRINIC [CONGO TELECOM] Route 102.204.204.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OA9-AFRINIC [OXAHOST] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 102.204.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-SAL7-AFRINIC [Serverpulse Africa Ltd] Route 102.204.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-SAL7-AFRINIC [Serverpulse Africa Ltd] Route 102.205.24.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GVAG2-AFRINIC [GROUP VIVENDI AFRICA GHANA LIMITED] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.205.36.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GVAG1-AFRINIC [GRP VIVENDI AFRICA GVA NIGERIA LIMITED] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.205.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214354] Prefix was owned by ORG-SAL6-AFRINIC [Sitehub Agency Ltd] Route 102.205.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214354] Prefix was owned by ORG-SAL6-AFRINIC [Sitehub Agency Ltd] Route 102.205.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-AMS5-AFRINIC [AFR-IX MAURITANIE - SARL] Route 102.205.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-CL23-AFRINIC [123 NET CPT (PTY) LTD] Route 102.205.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213481] Prefix was owned by ORG-HCSL1-AFRINIC [HEVIS CO SYSTEMS (PTY) LTD] Route 102.205.240.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213481] Prefix was owned by ORG-HCSL1-AFRINIC [HEVIS CO SYSTEMS (PTY) LTD] Route 102.205.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213481] Prefix was owned by ORG-HCSL1-AFRINIC [HEVIS CO SYSTEMS (PTY) LTD] Route 102.206.16.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.206.20.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.206.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211619] Prefix was owned by ORG-MFGD1-AFRINIC [Maxko for Gaming Development] Route 102.206.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211619] Prefix was owned by ORG-MFGD1-AFRINIC [Maxko for Gaming Development] Route 102.206.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211619] Prefix was owned by ORG-MFGD1-AFRINIC [Maxko for Gaming Development] Route 102.206.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211619] Prefix was owned by ORG-MFGD1-AFRINIC [Maxko for Gaming Development] Route 102.206.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CS14-AFRINIC [COMTECH sarl] Route 102.206.82.0/23 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AIT1-AFRINIC [ARC International Telecoms] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 102.206.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207113] Prefix was owned by ORG-WISP2-AFRINIC [Wavex Internet Service Provider LTD] Route 102.206.240.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GR1-AFRINIC [GVA RDC] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.207.28.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.207.72.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GB2-AFRINIC [GVA BENIN] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.207.108.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GVAU1-AFRINIC [Group Vivendi Africa Uganda Limited] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.208.68.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.208.69.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.208.120.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GR1-AFRINIC [GVA RDC] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.208.152.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.208.192.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JIL2-AFRINIC [Jenny Internet (Pty) Ltd] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.208.216.0/24 [AS328364] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZSL1-AFRINIC [Zettabyte Storage (Pty) Ltd] but owned by ORG-CTML1-AFRINIC [Host Africa (Pty) Ltd] Route 102.208.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16509] Prefix was owned by ORG-TARL1-AFRINIC [Thinkst Applied Research (PTY) Limited] Route 102.208.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16509] Prefix was owned by ORG-TARL1-AFRINIC [Thinkst Applied Research (PTY) Limited] Route 102.208.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14618] Prefix was owned by ORG-TARL1-AFRINIC [Thinkst Applied Research (PTY) Limited] Route 102.208.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14618] Prefix was owned by ORG-TARL1-AFRINIC [Thinkst Applied Research (PTY) Limited] Route 102.209.28.0/22 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WNL2-AFRINIC [WIOCC Nigeria Limited] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 102.209.29.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WNL2-AFRINIC [WIOCC Nigeria Limited] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 102.209.31.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WNL2-AFRINIC [WIOCC Nigeria Limited] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 102.209.32.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AAFT2-AFRINIC [Alhadatha Alalamiya for telecommunications and information technology L.L.C] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.209.36.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.209.92.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.209.128.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.209.132.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.209.176.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JISL1-AFRINIC [Jenny Internet Swaziland (Pty) Ltd] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.209.237.0/24 [AS328271] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IADC1-AFRINIC [IX AFRICA DATA CENTRE LIMITED] but owned by ORG-SSL3-AFRINIC [Syokinet Solutions Limited] Route 102.209.242.0/24 [AS329386] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ACAL1-AFRINIC [Abantu Cloud Africa (Pty) Ltd] but owned by ORG-NC8-AFRINIC [Neurotel Communications] Route 102.209.243.0/24 [AS329249] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ACAL1-AFRINIC [Abantu Cloud Africa (Pty) Ltd] but owned by ORG-DCWP1-AFRINIC [Dolphin Coast Wireless Pty Ltd] Route 102.210.60.0/22 [AS327814] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KDIS1-AFRINIC [Koncept Digital Integrated Services Limited] but owned by ORG-ECO1-AFRINIC [Ecoband Ltd] Route 102.210.84.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.210.144.0/24 [AS328364] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EDL1-AFRINIC [EAC directory Limited] but owned by ORG-CTML1-AFRINIC [Host Africa (Pty) Ltd] Route 102.210.145.0/24 [AS37497] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EDL1-AFRINIC [EAC directory Limited] but owned by ORG-NPL3-AFRINIC [Network Platforms (PTY) LTD] Route 102.210.146.0/24 [AS329184] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EDL1-AFRINIC [EAC directory Limited] but owned by ORG-CTML1-AFRINIC [Host Africa (Pty) Ltd] Route 102.210.147.0/24 [AS329184] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EDL1-AFRINIC [EAC directory Limited] but owned by ORG-CTML1-AFRINIC [Host Africa (Pty) Ltd] Route 102.210.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS100] Prefix was owned by ORG-FSBP1-AFRINIC [FIBRE SOURCING BOTSWANA PROPRIETARY LIMITED] Route 102.210.180.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.210.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16509] Prefix was owned by ORG-BOL1-AFRINIC [Byte Orbit (PTY) LTD] Route 102.210.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16509] Prefix was owned by ORG-BOL1-AFRINIC [Byte Orbit (PTY) LTD] Route 102.211.0.0/22 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OADC1-AFRINIC [Open Access Data Centres (Mauritius) Ltd] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 102.211.32.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.211.44.0/22 [AS328735] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LPL2-AFRINIC [Lunafibre Pty Ltd] but owned by ORG-FGPL1-AFRINIC [Fibre Geeks Pty Ltd] Route 102.211.60.0/22 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.211.60.0/23 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.211.62.0/23 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.211.88.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.211.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-DGFT1-AFRINIC [Digital Group for Telecom and Informatics Co] Route 102.211.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS39151] Prefix was owned by ORG-DGFT1-AFRINIC [Digital Group for Telecom and Informatics Co] Route 102.211.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CASE1-AFRINIC [COMPUTER AND SATELITE ELECTRONICS PTY LTD] Route 102.211.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-TPL4-AFRINIC [TouchBasePro PTY LTD] Route 102.211.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.211.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS56683] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.211.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.211.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137235] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.211.248.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.212.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215672] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.212.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211826] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.212.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212001] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.212.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-AOT1-AFRINIC [Alpha online Technology] Route 102.212.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-AIL3-AFRINIC [Abex Interconnects Limited] Route 102.212.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-AIL3-AFRINIC [Abex Interconnects Limited] Route 102.212.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-AIL3-AFRINIC [Abex Interconnects Limited] Route 102.212.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-AIL3-AFRINIC [Abex Interconnects Limited] Route 102.212.76.0/24 [AS328993] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL89-AFRINIC [SAWALINK LIMITED] but owned by ORG-CFCL1-AFRINIC [Click Fiber Communications Limited] Route 102.212.77.0/24 [AS328993] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL89-AFRINIC [SAWALINK LIMITED] but owned by ORG-CFCL1-AFRINIC [Click Fiber Communications Limited] Route 102.212.78.0/24 [AS328993] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL89-AFRINIC [SAWALINK LIMITED] but owned by ORG-CFCL1-AFRINIC [Click Fiber Communications Limited] Route 102.212.79.0/24 [AS328993] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL89-AFRINIC [SAWALINK LIMITED] but owned by ORG-CFCL1-AFRINIC [Click Fiber Communications Limited] Route 102.212.112.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.212.116.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.212.148.0/22 [AS328631] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IBC1-AFRINIC [Intrasurf Broadband cc] but owned by ORG-THC1-AFRINIC [TWC Hosting CC] Route 102.212.148.0/24 [AS328631] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IBC1-AFRINIC [Intrasurf Broadband cc] but owned by ORG-THC1-AFRINIC [TWC Hosting CC] Route 102.212.149.0/24 [AS328631] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IBC1-AFRINIC [Intrasurf Broadband cc] but owned by ORG-THC1-AFRINIC [TWC Hosting CC] Route 102.212.150.0/24 [AS328631] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IBC1-AFRINIC [Intrasurf Broadband cc] but owned by ORG-THC1-AFRINIC [TWC Hosting CC] Route 102.212.151.0/24 [AS328631] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IBC1-AFRINIC [Intrasurf Broadband cc] but owned by ORG-THC1-AFRINIC [TWC Hosting CC] Route 102.212.175.0/24 [AS37575] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PUOC1-AFRINIC [Public University of Cape Verde] but owned by ORG-TTS1-AFRINIC [UNITEL T+ Telecomunicacoes, Sociedade Unipessoal, S.A.] Route 102.212.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64945] Prefix was owned by ORG-MTN2-AFRINIC [MTN Zambia] Route 102.212.200.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JISL1-AFRINIC [Jenny Internet Swaziland (Pty) Ltd] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.212.208.0/24 [AS36920] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] but owned by ORG-KTL2-AFRINIC [KKON Technologies Ltd] Route 102.212.210.0/24 [AS37433] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] but owned by ORG-KTL2-AFRINIC [KKON Technologies Ltd] Route 102.212.211.0/24 [AS36920] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] but owned by ORG-KTL2-AFRINIC [KKON Technologies Ltd] Route 102.212.255.0/24 [AS328658] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PBSL1-AFRINIC [Pronto Broadband Solutions Limited] but owned by ORG-DCIL1-AFRINIC [De Choicetech Integrated Ltd] Route 102.213.36.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.213.48.0/22 [AS328856] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VFL1-AFRINIC [VUMA FIBER LIMITED] but owned by ORG-VCL7-AFRINIC [VIJIJI CONNECT LIMITED] Route 102.213.48.0/24 [AS328856] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VFL1-AFRINIC [VUMA FIBER LIMITED] but owned by ORG-VCL7-AFRINIC [VIJIJI CONNECT LIMITED] Route 102.213.49.0/24 [AS328856] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VFL1-AFRINIC [VUMA FIBER LIMITED] but owned by ORG-VCL7-AFRINIC [VIJIJI CONNECT LIMITED] Route 102.213.50.0/24 [AS328856] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VFL1-AFRINIC [VUMA FIBER LIMITED] but owned by ORG-VCL7-AFRINIC [VIJIJI CONNECT LIMITED] Route 102.213.51.0/24 [AS328856] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VFL1-AFRINIC [VUMA FIBER LIMITED] but owned by ORG-VCL7-AFRINIC [VIJIJI CONNECT LIMITED] Route 102.213.52.0/23 [AS37529] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CYHS1-AFRINIC [CACHU Y HERMANOS, S.L.] but owned by ORG-GdId1-AFRINIC [Gestora de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial] Route 102.213.140.0/23 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TTS2-AFRINIC [Tourvest Travel Services] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 102.213.152.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36236] Prefix was owned by ORG-NZ1-AFRINIC [NETACTUATE ZA] Route 102.213.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36236] Prefix was owned by ORG-NZ1-AFRINIC [NETACTUATE ZA] Route 102.213.164.0/23 [AS329429] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TL18-AFRINIC [TForge (Pty) Ltd] but owned by ORG-DSCP1-AFRINIC [Data Sciences Corporation Pty Ltd] Route 102.213.169.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 102.213.184.0/22 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOL3-AFRINIC [Africa Online (Africa) (Pty) Ltd] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 102.213.192.0/24 [AS36926] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSL5-AFRINIC [Cheetahnet Solutions Limited] but owned by ORG-CKL1-AFRINIC [Airtel Networks Kenya Limited] Route 102.213.195.0/24 [AS36926] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSL5-AFRINIC [Cheetahnet Solutions Limited] but owned by ORG-CKL1-AFRINIC [Airtel Networks Kenya Limited] Route 102.213.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29259] Prefix was owned by ORG-OS3-AFRINIC [Orioncom SPRL] Route 102.214.48.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.214.104.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.214.105.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.214.106.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.214.107.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.214.112.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JLPL1-AFRINIC [JENNY LESOTHO PTY LTD] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.214.148.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.214.167.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TACF1-AFRINIC [TAQNYAT ALJEEL COMPANY FOR COMMUNICATION AND INFORMATION TECHNOLOGY LTD] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.214.182.0/23 [AS327767] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DCC1-AFRINIC [Davo Corp CC] but owned by ORG-ULSC1-AFRINIC [Ultimate Linux Solutions (Pty) Ltd] Route 102.214.182.0/24 [AS327767] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DCC1-AFRINIC [Davo Corp CC] but owned by ORG-ULSC1-AFRINIC [Ultimate Linux Solutions (Pty) Ltd] Route 102.214.183.0/24 [AS327767] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DCC1-AFRINIC [Davo Corp CC] but owned by ORG-ULSC1-AFRINIC [Ultimate Linux Solutions (Pty) Ltd] Route 102.214.212.0/22 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOL3-AFRINIC [Africa Online (Africa) (Pty) Ltd] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 102.214.228.0/22 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AIT1-AFRINIC [ARC International Telecoms] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 102.214.228.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AIT1-AFRINIC [ARC International Telecoms] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 102.214.229.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AIT1-AFRINIC [ARC International Telecoms] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 102.214.230.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AIT1-AFRINIC [ARC International Telecoms] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 102.214.231.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AIT1-AFRINIC [ARC International Telecoms] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 102.214.247.0/24 [AS28683] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ES4-AFRINIC [EUPHORBIA SARL] but owned by ORG-SBDN1-AFRINIC [SOCIETE BENINOISE D'INFRASTRUCTURES NUMERIQUES] Route 102.215.24.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JISL1-AFRINIC [Jenny Internet Swaziland (Pty) Ltd] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.215.28.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.215.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14593] Prefix was owned by ORG-SISN1-AFRINIC [Starlink Internet Services Nigeria Ltd] Route 102.215.148.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.215.160.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.215.164.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.215.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-NEDL1-AFRINIC [N. E Diversified Limited] Route 102.215.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-NEDL1-AFRINIC [N. E Diversified Limited] Route 102.215.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-NEDL1-AFRINIC [N. E Diversified Limited] Route 102.215.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-NEDL1-AFRINIC [N. E Diversified Limited] Route 102.215.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-NEDL1-AFRINIC [N. E Diversified Limited] Route 102.215.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-RPDL1-AFRINIC [Rayv Product Development (Pty) Ltd] Route 102.215.196.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AECF1-AFRINIC [Al Ertikaz Co. for Internet Service & Information Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.215.197.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AECF1-AFRINIC [Al Ertikaz Co. for Internet Service & Information Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.215.198.0/23 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AECF1-AFRINIC [Al Ertikaz Co. for Internet Service & Information Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.215.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203963] Prefix was owned by ORG-DCL9-AFRINIC [DIPLOMAT COMMUNICATIONS (PTY) LTD] Route 102.215.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209179] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.215.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.215.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214795] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.215.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.215.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214279] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.215.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4766] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.215.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26042] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.215.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5065] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.216.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-BS5-AFRINIC [BLOOSAT SA] Route 102.216.39.0/24 [AS328659] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTL5-AFRINIC [Datacom Telecommunication Limited] but owned by ORG-VSL2-AFRINIC [Vobiss Solutions Limited] Route 102.216.60.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.216.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401838] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.216.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.216.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213738] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.216.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214879] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.216.137.0/24 [AS328611] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA71-AFRINIC [Serverlibya] but owned by ORG-LE2-AFRINIC [Libyan Elite Company for Technical Solutions] Route 102.216.138.0/24 [AS328611] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA71-AFRINIC [Serverlibya] but owned by ORG-LE2-AFRINIC [Libyan Elite Company for Technical Solutions] Route 102.216.139.0/24 [AS328611] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA71-AFRINIC [Serverlibya] but owned by ORG-LE2-AFRINIC [Libyan Elite Company for Technical Solutions] Route 102.216.144.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.216.148.0/22 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.216.148.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.216.149.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.216.150.0/23 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.216.244.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.217.56.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.217.57.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.217.58.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.217.80.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.217.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-ATN3-AFRINIC [Afr-ix Telecom Niger] Route 102.217.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399073] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.217.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399861] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.217.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395839] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.217.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212609] Prefix was owned by ORG-BA18-AFRINIC [Bonus 1000F] Route 102.217.136.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.217.137.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.217.138.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.217.139.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.217.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 102.217.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 102.217.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 102.217.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-KCL2-AFRINIC [KAOPU CLOUD (NIGERIA) LIMITED] Route 102.217.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-KCL2-AFRINIC [KAOPU CLOUD (NIGERIA) LIMITED] Route 102.217.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-KCL2-AFRINIC [KAOPU CLOUD (NIGERIA) LIMITED] Route 102.217.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-KCL2-AFRINIC [KAOPU CLOUD (NIGERIA) LIMITED] Route 102.218.28.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.218.36.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.218.37.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.218.38.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.218.39.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.218.42.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IIL3-AFRINIC [IMVULA ITECHNOLOGIES (PTY) LTD] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 102.218.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NSL5-AFRINIC [NetIT Solutions LTD] Route 102.218.108.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GVAU1-AFRINIC [Group Vivendi Africa Uganda Limited] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.218.224.0/24 [AS329176] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCL4-AFRINIC [GOIL COMPANY LIMITED] but owned by ORG-FTST1-AFRINIC [Future Technology Solutions Today Limited] Route 102.219.12.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.219.13.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.219.14.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.219.15.0/24 [AS329181] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OWPL1-AFRINIC [One Wireless Pty Ltd] but owned by ORG-BT3-AFRINIC [Bluedog Technology] Route 102.219.20.0/24 [AS328631] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IBC1-AFRINIC [Intrasurf Broadband cc] but owned by ORG-THC1-AFRINIC [TWC Hosting CC] Route 102.219.28.0/24 [AS32860] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TNEC1-AFRINIC [The National Examinations Council of Tanzania] but owned by ORG-CL5-AFRINIC [Cats-Net Limited] Route 102.219.29.0/24 [AS37611] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCSC1-AFRINIC [MODEM COMPUTER SERVICES (PTY) LTD] but owned by ORG-AS7-AFRINIC [AFRIHOST SP (PTY) LTD] Route 102.219.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-ATCS1-AFRINIC [AFR-IX TELECOM CAMEROUN SARL] Route 102.219.93.0/24 [AS11845] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EL9-AFRINIC [Everlytic (Pty) Ltd] but owned by ORG-DPBO1-AFRINIC [Vox Telecom Ltd] Route 102.219.100.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.219.101.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.219.102.0/23 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.219.120.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.219.152.0/24 [AS329267] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KTL2-AFRINIC [KKON Technologies Ltd] but owned by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] Route 102.219.154.0/24 [AS329267] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KTL2-AFRINIC [KKON Technologies Ltd] but owned by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] Route 102.219.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44592] Prefix was owned by ORG-CL21-AFRINIC [cybrscrb ltd.] Route 102.219.216.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.219.224.0/23 [AS37314] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RPL1-AFRINIC [Redefine Properties Limited] but owned by ORG-SI4-AFRINIC [Inq Digital South Africa (Pty) Ltd] Route 102.219.227.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AAMC1-AFRINIC [ALKAFAA AL MUTAQADEMA COMPANY] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.220.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UDBL1-AFRINIC [UGANDA DEVELOPMENT BANK LIMITED] Route 102.220.28.0/22 [AS36947] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AT9-AFRINIC [ADEX Technology] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 102.220.52.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VCPL2-AFRINIC [VTS Connect Pty Ltd] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 102.220.56.0/23 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GR1-AFRINIC [GVA RDC] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.220.58.0/23 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GR1-AFRINIC [GVA RDC] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 102.220.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55933] Prefix was owned by ORG-SNCL1-AFRINIC [Sun Network Company Limited] Route 102.220.92.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.220.94.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.220.95.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.220.100.0/24 [AS37153] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OMNP1-AFRINIC [One Mobile Networks Pty Ltd] but owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 102.220.140.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BAfD1-AFRINIC [Bait Ashames for Data Communication] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.220.142.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BAfD1-AFRINIC [Bait Ashames for Data Communication] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.220.143.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BAfD1-AFRINIC [Bait Ashames for Data Communication] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.220.160.0/22 [AS36873] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FWIE1-AFRINIC [Flash Wireless ISP Enterprises] but owned by ORG-VNL1-AFRINIC [Airtel Networks Limited] Route 102.220.198.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AT5-AFRINIC [AIRTEL TCHAD] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 102.220.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CASE1-AFRINIC [COMPUTER AND SATELITE ELECTRONICS PTY LTD] Route 102.220.251.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WTL5-AFRINIC [Wananchi Telecom Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.221.8.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AAFT2-AFRINIC [Alhadatha Alalamiya for telecommunications and information technology L.L.C] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.221.20.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.221.24.0/22 [AS37100] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MC6-AFRINIC [Seacom Western Cape (Pty) Ltd] but owned by ORG-SL75-AFRINIC [SEACOM Limited] Route 102.221.40.0/22 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EILI1-AFRINIC [Elu Investments Limited (Incorporated in Ireland) External Profit Company] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 102.221.50.0/23 [AS37153] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-HL4-AFRINIC [Hostking (Pty) Ltd] but owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 102.221.56.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCaT1-AFRINIC [Manara Communication and Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.221.57.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCaT1-AFRINIC [Manara Communication and Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.221.58.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCaT1-AFRINIC [Manara Communication and Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.221.59.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCaT1-AFRINIC [Manara Communication and Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.221.75.0/24 [AS37209] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BCTL1-AFRINIC [BAT Computer Technologies Limited] but owned by ORG-HL1-AFRINIC [Hyperia Limited] Route 102.221.96.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CS14-AFRINIC [COMTECH sarl] Route 102.221.116.0/24 [AS36978] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VA69-AFRINIC [valU] but owned by ORG-EHH1-AFRINIC [EFG Hermes Holding] Route 102.221.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-ESU1-AFRINIC [Ekiti State University] Route 102.221.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.221.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.221.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.221.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63293] Prefix was owned by ORG-FSAL1-AFRINIC [Facebook South Africa (Pty) Ltd] Route 102.221.240.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JISL2-AFRINIC [Jenny Internet Services Ltd] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.222.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-IAKL1-AFRINIC [ISAT AFRICA KENYA LTD] Route 102.222.48.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JIL2-AFRINIC [Jenny Internet (Pty) Ltd] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.222.68.0/23 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.222.70.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCUL1-AFRINIC [WANANCHI CABLE UGANDA LIMITED (SINGLE)] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.222.84.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WCL4-AFRINIC [WANANCHI CABLE (T) LIMITED] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 102.222.88.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JIL1-AFRINIC [Jenny Internet LDA] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.222.100.0/23 [AS328365] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZA3-AFRINIC [ZANOG] but owned by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] Route 102.222.100.0/24 [AS328365] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZA3-AFRINIC [ZANOG] but owned by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] Route 102.222.101.0/24 [AS328365] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZA3-AFRINIC [ZANOG] but owned by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] Route 102.222.102.0/23 [AS328365] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZA3-AFRINIC [ZANOG] but owned by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] Route 102.222.132.0/22 [AS327750] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JISL1-AFRINIC [Jenny Internet Swaziland (Pty) Ltd] but owned by ORG-JIc1-AFRINIC [JENNY INTERNET (PTY) LTD] Route 102.222.138.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS800] Prefix was owned by ORG-WSAL1-AFRINIC [WorldVu South Africa (Pty) Ltd] Route 102.222.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS800] Prefix was owned by ORG-WSAL1-AFRINIC [WorldVu South Africa (Pty) Ltd] Route 102.222.152.0/22 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ABML1-AFRINIC [Al Bayan Media Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 102.222.156.0/24 [AS37739] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL39-AFRINIC [Intaweb (Pty) Ltd.] but owned by ORG-ACAL1-AFRINIC [Abantu Cloud Africa (Pty) Ltd] Route 102.222.157.0/24 [AS37739] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL39-AFRINIC [Intaweb (Pty) Ltd.] but owned by ORG-ACAL1-AFRINIC [Abantu Cloud Africa (Pty) Ltd] Route 102.222.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-ATL5-AFRINIC [AFR-IX TELECOM LIMITED] Route 102.222.212.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DMS1-AFRINIC [Datapacket Maroc SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 102.222.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201011] Prefix was owned by ORG-DMS1-AFRINIC [Datapacket Maroc SARL] Route 102.222.252.0/23 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AECF1-AFRINIC [Al Ertikaz Co. for Internet Service & Information Technology] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 102.223.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-ADCL1-AFRINIC [AFR-IX DATA COMMUNICATIONS LIMITED] Route 102.223.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-MTMS1-AFRINIC [M'DATA TELECOM MALI SARL] Route 102.223.76.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 102.223.77.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 102.223.78.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 102.223.79.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 102.223.96.0/22 [AS37358] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KL8-AFRINIC [Kaltrade 470 (Pty) Ltd] but owned by ORG-BA10-AFRINIC [BitCo] Route 102.223.96.0/24 [AS37358] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KL8-AFRINIC [Kaltrade 470 (Pty) Ltd] but owned by ORG-BA10-AFRINIC [BitCo] Route 102.223.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215354] Prefix was owned by ORG-AAL3-AFRINIC [ANGELHOSTING AFRICA (PTY) LTD] Route 102.223.116.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL4-AFRINIC [Elements Cloud Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 102.223.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-RPDL1-AFRINIC [Rayv Product Development (Pty) Ltd] Route 102.223.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-RPDL1-AFRINIC [Rayv Product Development (Pty) Ltd] Route 102.223.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-RPDL1-AFRINIC [Rayv Product Development (Pty) Ltd] Route 102.223.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-RPDL1-AFRINIC [Rayv Product Development (Pty) Ltd] Route 102.223.154.0/23 [AS329109] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MOIA1-AFRINIC [Ministry of Information and Communications, Government of Sierra Leone] but owned by ORG-ZL5-AFRINIC [Zoodlabs(SL) Limited] Route 102.223.159.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OAFT1-AFRINIC [Ozone aljadid for telecom and technology LLC] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 102.223.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 102.223.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 102.223.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 102.223.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 102.223.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-ZL2-AFRINIC [Zarclear (Pty) Ltd] Route 102.223.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS328621] Prefix was owned by ORG-BA16-AFRINIC [BIZVOIP] Route 102.223.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS328621] Prefix was owned by ORG-BA16-AFRINIC [BIZVOIP] Route 102.223.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS328621] Prefix was owned by ORG-BA16-AFRINIC [BIZVOIP] Route 102.223.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS328621] Prefix was owned by ORG-BA16-AFRINIC [BIZVOIP] Route 102.240.0.0/14 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 105.73.96.0/22 [AS30983] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MC5-AFRINIC [Wana Corporate] but owned by ORG-CNpl1-AFRINIC [CNRST (Centre National pour la Recherche Scientifique et Technique)] Route 105.112.0.0/12 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141180] Prefix was owned by ORG-VNL1-AFRINIC [Airtel Networks Limited] Route 105.112.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141180] Prefix was owned by ORG-VNL1-AFRINIC [Airtel Networks Limited] Route 105.114.24.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VNL1-AFRINIC [Airtel Networks Limited] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 105.235.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198381] Prefix was owned by ORG-RA4-AFRINIC [RCS-Communication] Route 105.247.11.0/24 [AS329012] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VA67-AFRINIC [Vodacom] but owned by ORG-MCL8-AFRINIC [Motus Corporation (Pty) Ltd] Route 129.122.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49902] Prefix was owned by ORG-SRdR1-AFRINIC [Societe Reunionnaise du Radiotelephone] Route 129.205.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2] Prefix was owned by ORG-KT1-AFRINIC [KAB Technologies] Route 137.63.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32489] Prefix was owned by ORG-AC5-AFRINIC [AfriTel Corporation] Route 137.196.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS10] Prefix was owned by ORG-ZM1-AFRINIC [Airtel Malawi Ltd] Route 137.214.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FRD1-AFRINIC [Foundation for Research Development] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 137.214.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FRD1-AFRINIC [Foundation for Research Development] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 137.214.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FRD1-AFRINIC [Foundation for Research Development] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 137.215.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 137.215.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 137.215.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 139.26.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202023] Prefix was owned by ORG-TOS1-AFRINIC [TELCO OI SAS] Route 139.26.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202023] Prefix was owned by ORG-TOS1-AFRINIC [TELCO OI SAS] Route 139.26.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202023] Prefix was owned by ORG-TOS1-AFRINIC [TELCO OI SAS] Route 139.26.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202023] Prefix was owned by ORG-TOS1-AFRINIC [TELCO OI SAS] Route 139.26.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202023] Prefix was owned by ORG-TOS1-AFRINIC [TELCO OI SAS] Route 139.53.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL17-AFRINIC [ArcelorMittal South Africa Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 143.128.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ217-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 143.128.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ217-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 143.128.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ217-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.5.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.8.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.19.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.24.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.25.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.28.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.58.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.80.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.84.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.85.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.86.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.64.216.0/21 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CSIR1-AFRINIC [CSIR - Council for Scientific and Industrial Research] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.141.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UotW1-AFRINIC [University of the Witwatersrand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.230.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ217-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.230.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ217-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.230.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ217-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.232.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UoS2-AFRINIC [University of Stellenbosch] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 146.232.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UoS2-AFRINIC [University of Stellenbosch] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.2.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.5.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.6.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.8.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.18.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.19.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.99.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.102.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.120.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.106.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RAU1-AFRINIC [University of Johannesburg] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.107.0.0/16 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VoSA1-AFRINIC [Volkswagen of South Africa] but owned by ORG-VA67-AFRINIC [Vodacom] Route 152.108.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.108.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 152.111.0.0/16 [AS10474] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.1.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.2.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.3.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.4.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.5.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.6.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.8.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.9.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.10.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.11.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.12.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.14.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.15.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.16.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.17.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.18.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.19.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.20.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.21.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.22.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.23.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.24.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.25.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.26.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.27.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.28.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.29.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.30.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.31.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.32.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.33.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.34.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.35.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.36.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.37.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.41.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.43.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.44.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.44.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.45.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.46.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.47.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.50.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.51.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.53.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.54.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.55.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.56.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.57.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.59.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.60.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.61.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.63.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.64.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.66.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.67.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.68.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.69.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.70.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.72.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.73.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.74.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.77.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.78.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.79.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.80.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.81.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.82.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.83.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.84.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.85.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.86.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.87.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.88.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.90.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.91.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.92.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.94.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.95.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.96.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.97.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.99.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.100.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.101.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.102.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.103.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.104.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.105.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.106.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.106.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.108.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.109.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.130.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.131.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.132.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.133.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.134.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.135.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.136.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.137.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.139.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.140.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.142.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.143.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.144.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.145.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.146.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.147.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.148.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.150.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.151.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.154.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.156.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.157.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.159.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.160.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.162.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.163.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.165.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.166.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.167.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.168.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.172.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.174.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.177.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.180.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.181.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.182.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.183.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.185.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.186.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.187.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.188.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.189.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.190.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.191.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.192.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.193.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.194.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.195.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.196.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.197.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.198.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.200.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.201.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.203.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.204.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.205.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.206.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.207.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.208.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.209.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.210.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.211.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.212.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.213.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.214.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.215.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.216.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.217.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.219.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.220.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.221.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.222.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.223.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.224.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.225.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.226.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.228.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.229.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.230.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.231.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.232.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.232.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.233.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.234.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.235.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.238.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.239.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.240.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.241.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.242.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.244.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.245.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.246.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.247.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.248.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.250.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.251.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.252.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.111.254.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA18-AFRINIC [Naspers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 152.112.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-HSRC1-AFRINIC [Human Science Research Council] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.112.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-HSRC1-AFRINIC [Human Science Research Council] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 152.112.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-HSRC1-AFRINIC [Human Science Research Council] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 154.0.189.0/24 [AS36873] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AGS2-AFRINIC [Airtel Gabon S.A] but owned by ORG-VNL1-AFRINIC [Airtel Networks Limited] Route 154.0.192.0/18 [AS22735] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OotP1-AFRINIC [Office of the Prime Minister] but owned by ORG-GotR1-AFRINIC [Government of the Republic of Namibia] Route 154.0.192.0/19 [AS22735] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OotP1-AFRINIC [Office of the Prime Minister] but owned by ORG-GotR1-AFRINIC [Government of the Republic of Namibia] Route 154.0.192.0/20 [AS22735] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OotP1-AFRINIC [Office of the Prime Minister] but owned by ORG-GotR1-AFRINIC [Government of the Republic of Namibia] Route 154.16.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48314] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42831] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS43350] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7018] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20141] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS43350] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400909] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38001] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.26.0/24 [AS29614] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NL4-AFRINIC [NetStack Ltd] but owned by ORG-GTCL1-AFRINIC [Ghana Telecommunications Company Limited] Route 154.16.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138997] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210576] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400039] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32159] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11351] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212335] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211440] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16509] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.62.0/24 [AS329384] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NL4-AFRINIC [NetStack Ltd] but owned by ORG-BEAP1-AFRINIC [Bakwena Entertainment and Production Services (PTY) Ltd] Route 154.16.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211440] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400909] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400909] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397373] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18345] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4637] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212384] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399641] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60781] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201341] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211373] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397373] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60542] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.126.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399838] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399838] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399838] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141158] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209181] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14670] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32181] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200017] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212384] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212669] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397384] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.160.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NL4-AFRINIC [NetStack Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 154.16.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137409] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8220] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11426] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS53340] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60602] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215224] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147261] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198100] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400040] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211192] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20278] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62943] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29713] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400866] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22168] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS216193] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22168] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.232.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138997] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400040] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22168] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138997] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20454] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54252] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397373] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16509] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22168] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13213] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS216193] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.16.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213734] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.65.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2] Prefix was owned by ORG-KT1-AFRINIC [KAB Technologies] Route 154.65.66.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396982] Prefix was owned by ORG-DNSL1-AFRINIC [AVOXI (PTY) LTD] Route 154.66.216.0/22 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 154.66.217.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 154.66.218.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 154.66.219.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL78-AFRINIC [SIMBANET (U) LIMITED] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 154.66.229.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCSL1-AFRINIC [Mauritius Computing Services Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 154.67.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21351] Prefix was owned by ORG-MA29-AFRINIC [CANAL + TELECOM] Route 154.67.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21351] Prefix was owned by ORG-MA29-AFRINIC [CANAL + TELECOM] Route 154.67.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21351] Prefix was owned by ORG-MA29-AFRINIC [CANAL + TELECOM] Route 154.67.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21351] Prefix was owned by ORG-MA29-AFRINIC [CANAL + TELECOM] Route 154.70.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62390] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.70.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.70.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.70.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212384] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.70.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-CS11-AFRINIC [COMSATES SARL] Route 154.70.194.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-CS11-AFRINIC [COMSATES SARL] Route 154.70.200.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.70.201.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.70.202.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.70.203.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.70.204.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.70.205.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.70.206.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.70.207.0/24 [AS37738] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PMS2-AFRINIC [PIXI MEDIA SARL] but owned by ORG-HA4-AFRINIC [HOSTOWEB] Route 154.72.33.0/24 [AS36970] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL27-AFRINIC [Interswitch Limited] but owned by ORG-IL19-AFRINIC [IPARTNERS LIMITED] Route 154.72.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4809] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4134] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4809] Prefix was owned by ORG-CTSA1-AFRINIC [China Telecom South Africa (Pty) Ltd.] Route 154.72.53.0/24 [AS328442] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IA48-AFRINIC [ITM] but owned by ORG-US12-AFRINIC [United SA] Route 154.72.54.0/24 [AS328442] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IA48-AFRINIC [ITM] but owned by ORG-US12-AFRINIC [United SA] Route 154.72.55.0/24 [AS328442] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IA48-AFRINIC [ITM] but owned by ORG-US12-AFRINIC [United SA] Route 154.72.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.68.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.80.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 154.72.240.0/20 [AS37100] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PA13-AFRINIC [Pamoja, Ltd] but owned by ORG-SL75-AFRINIC [SEACOM Limited] Route 154.73.28.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 154.73.29.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 154.73.30.0/24 [AS21003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RL1-AFRINIC [RAWAFED LIBYA] but owned by ORG-GPaT1-AFRINIC [General Post and Telecommunication Company (GPTC)] Route 154.73.48.0/24 [AS37721] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA65-AFRINIC [1tel S.A.] but owned by ORG-VTS1-AFRINIC [Virtual Technologies & Solutions] Route 154.73.49.0/24 [AS37721] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA65-AFRINIC [1tel S.A.] but owned by ORG-VTS1-AFRINIC [Virtual Technologies & Solutions] Route 154.73.52.0/23 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCaT1-AFRINIC [Manara Communication and Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 154.73.54.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCaT1-AFRINIC [Manara Communication and Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 154.73.55.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MCaT1-AFRINIC [Manara Communication and Technology] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 154.73.92.0/22 [AS36947] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EBSe1-AFRINIC [Electronic Business Services eBS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.73.108.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TIaC1-AFRINIC [Trans-Sahara IT and Communication] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 154.73.110.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TIaC1-AFRINIC [Trans-Sahara IT and Communication] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 154.73.111.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TIaC1-AFRINIC [Trans-Sahara IT and Communication] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 154.73.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-iAZL1-AFRINIC [iSAT Africa Zambia Ltd] Route 154.73.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 154.73.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 154.73.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 154.73.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 154.80.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.80.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4755] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.138.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.142.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17497] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.208.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16437] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16437] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16437] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.224.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.81.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14315] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.64.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.100.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.126.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142629] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142629] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142629] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.136.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401615] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.138.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142629] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142629] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150000] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150000] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.162.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.176.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.178.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.82.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133180] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38638] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.22.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272092] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.42.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.74.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.76.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214808] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.138.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.146.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.150.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.83.240.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.83.240.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.83.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58073] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211392] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211392] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133180] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27947] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141216] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS204044] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.188.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.84.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45194] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401434] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401615] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.24.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.44.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.56.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18004] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18004] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18004] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149981] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9287] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40950] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.126.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.85.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214156] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.20.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.22.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.24.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136897] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136897] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136897] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136897] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.86.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.87.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138678] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400999] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132546] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.36.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.88.40.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.88.42.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.64.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4760] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64126] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64126] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271988] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272040] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272040] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS274035] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272011] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271956] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271956] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS264605] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS264605] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS264605] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.88.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS264605] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150150] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63969] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22724] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210334] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.148.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55933] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.158.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.89.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.32.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.34.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.36.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.42.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.44.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.46.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.48.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.50.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.54.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.62.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63023] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.90.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398478] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58944] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201390] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133012] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140570] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140570] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29684] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.37.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.91.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.146.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152920] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152920] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.164.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38638] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38638] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.172.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.91.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152179] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.204.0/22 [AS25818] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-cA1-AFRINIC [cmcnetworks] Route 154.91.208.0/20 [AS25818] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-cA1-AFRINIC [cmcnetworks] Route 154.91.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.91.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.0.0/14 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149641] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18004] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.96.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.132.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133847] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398478] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136501] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136501] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136501] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.92.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23338] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134687] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134687] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134687] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134687] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.24.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132825] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.34.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.36.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.42.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.54.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.84.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140666] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140666] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140666] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.100.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.104.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.112.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.124.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.93.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63023] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133180] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133180] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133180] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133180] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.20.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.54.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.66.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140666] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.94.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.36.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.120.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.122.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140666] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.150.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.95.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.114.25.0/24 [AS36982] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UCT1-AFRINIC [University of Cape Town] Route 154.115.112.0/20 [AS36982] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UCT1-AFRINIC [University of Cape Town] Route 154.120.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 154.120.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 154.120.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 154.120.233.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 154.120.238.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 154.120.245.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 154.121.0.0/16 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.5.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.8.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.13.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.14.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.16.0/21 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.16.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.17.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.18.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.19.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.20.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.21.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.22.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.23.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.24.0/21 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.32.0/21 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.40.0/21 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.40.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.41.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.42.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.43.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.44.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.45.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.46.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.47.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.48.0/20 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.65.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.66.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.70.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.72.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.74.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.76.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.76.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.77.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.78.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.80.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.82.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.84.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.86.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.88.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.90.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.90.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.91.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.92.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.94.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.96.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.96.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.97.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.98.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.100.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.102.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.104.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.106.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.106.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.107.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.108.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.110.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.112.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.114.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.116.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.118.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.120.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.122.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.124.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.126.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.128.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.130.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.132.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.132.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.133.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.134.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.134.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.135.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.136.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.136.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.137.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.138.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.142.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.144.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.146.0/23 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.200.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.121.251.0/24 [AS327712] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATMM1-AFRINIC [Algerie Telecom Mobile MOBILIS] but owned by ORG-TA23-AFRINIC [Telecom Algeria] Route 154.124.0.0/15 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.124.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.125.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 154.126.128.0/24 [AS15964] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NAFI1-AFRINIC [NATIONAL AGENCY FOR INFORMATION AND COMMUNICATION TECHNOLOGIES] but owned by ORG-IA6-AFRINIC [CAMTEL] Route 154.126.129.0/24 [AS15964] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NAFI1-AFRINIC [NATIONAL AGENCY FOR INFORMATION AND COMMUNICATION TECHNOLOGIES] but owned by ORG-IA6-AFRINIC [CAMTEL] Route 154.126.132.0/24 [AS15964] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NAFI1-AFRINIC [NATIONAL AGENCY FOR INFORMATION AND COMMUNICATION TECHNOLOGIES] but owned by ORG-IA6-AFRINIC [CAMTEL] Route 154.127.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-ZCL1-AFRINIC [Zee Communications Ltd] Route 154.127.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62390] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS154049] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396073] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397373] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21840] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399073] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139989] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.127.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211440] Prefix was owned by ORG-NL4-AFRINIC [NetStack Ltd] Route 154.176.0.0/12 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.176.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.177.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.178.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.178.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.178.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.178.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.178.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.179.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.180.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.180.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.180.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.180.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.182.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.183.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.184.0.0/13 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.184.0.0/15 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.186.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.187.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.188.0.0/14 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.190.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.191.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 154.192.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.192.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23674] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.108.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.156.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.158.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.186.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.208.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214432] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214432] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.193.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.0.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.194.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38193] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272854] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272854] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215123] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151610] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151610] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51896] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272854] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141718] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.46.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.48.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150900] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14315] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38638] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9123] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9123] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272854] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211826] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29852] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.64.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS52263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.164.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.192.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.212.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.216.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.224.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.232.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.234.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.194.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134365] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.195.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28087] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14315] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400999] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142132] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17497] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.170.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.224.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141389] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141389] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.196.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272854] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.34.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262191] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139339] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139339] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18233] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140659] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209824] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273147] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139871] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211826] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132546] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139871] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211826] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27947] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22846] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22846] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.122.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.197.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60171] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.197.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58460] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137184] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137184] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137184] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20457] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38264] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15221] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134365] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS267834] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS267834] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS267834] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS267834] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS267834] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45669] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142002] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.166.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27947] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.184.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.186.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.198.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.68.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.199.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273882] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140224] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140224] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273155] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273155] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273155] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.200.248.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140883] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150698] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.8.0/21 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.201.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.14.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.201.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397630] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.48.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.201.52.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.201.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54252] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54252] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54252] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.64.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.74.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.76.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.78.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.92.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.94.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401075] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401075] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401075] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS197730] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS197730] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.124.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS197730] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.126.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.201.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138678] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26617] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26617] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215691] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.80.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.80.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.81.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.82.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.83.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.84.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.84.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.85.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.202.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.118.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.202.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS146993] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.48.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.64.0/21 [AS37517] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-CVTS1-AFRINIC [CABO VERDE TELECOM, S.A] Route 154.203.64.0/22 [AS37517] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-CVTS1-AFRINIC [CABO VERDE TELECOM, S.A] Route 154.203.68.0/22 [AS37517] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-CVTS1-AFRINIC [CABO VERDE TELECOM, S.A] Route 154.203.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.128.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.144.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.154.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.232.0/21 [AS37517] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-CVTS1-AFRINIC [CABO VERDE TELECOM, S.A] Route 154.203.232.0/22 [AS37517] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-CVTS1-AFRINIC [CABO VERDE TELECOM, S.A] Route 154.203.236.0/22 [AS37517] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-CVTS1-AFRINIC [CABO VERDE TELECOM, S.A] Route 154.203.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.203.252.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.203.253.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.203.254.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.203.255.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.204.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151196] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151196] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151196] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151196] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151196] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.204.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45996] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45996] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.136.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.142.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137510] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201411] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.205.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142132] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.62.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.68.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.74.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.76.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.80.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.82.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.84.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.92.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.94.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.96.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.98.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.100.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.102.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.104.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.108.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.110.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.112.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.114.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.116.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.118.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.206.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.102.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.114.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.124.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.140.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.224.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.207.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.64.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.128.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS270157] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152920] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152920] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152920] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152920] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.208.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137962] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137962] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141109] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141109] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.128.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.209.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214449] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.248.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.209.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18229] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135845] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135845] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150008] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.210.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.211.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.140.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.144.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.146.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151196] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45753] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.162.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151196] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.212.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63673] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63673] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63673] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4760] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.64.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.213.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS174] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.34.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.36.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.42.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.44.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.46.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.48.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.50.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.54.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.192.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.193.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.195.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.196.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.197.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS47890] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.199.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.200.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.201.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.202.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.203.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.204.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS47890] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.206.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.207.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.210.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.211.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.212.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS47890] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.214.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.215.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.217.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.218.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2914] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.220.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.221.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.222.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.214.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2914] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.214.224.0/19 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 154.215.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38638] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS147176] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.215.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137962] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.216.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS33223] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.176.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.234.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18978] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.217.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61414] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.96.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.218.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.120.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.122.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.124.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.126.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.219.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.220.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134175] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.221.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131618] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135391] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140659] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140659] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.74.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2914] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.80.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.82.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.84.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.118.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS204548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.136.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.146.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395201] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.222.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133448] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137962] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137962] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.34.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.54.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.62.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.66.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.68.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.74.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.76.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.78.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS271990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49505] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.230.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.223.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 154.236.0.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.16.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.25.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.26.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.27.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.28.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.29.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.30.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.31.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.32.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.33.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.64.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.65.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.66.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.68.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.69.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.70.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.71.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.76.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.77.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.78.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.80.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.81.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.82.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.83.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.84.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.86.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.87.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.88.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.96.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.112.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.128.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.128.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.136.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.144.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.152.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.160.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.162.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.163.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.165.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.166.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.167.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.168.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.168.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.170.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.171.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.172.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.173.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.174.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.175.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.176.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.176.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.177.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.178.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.179.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.180.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.181.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.182.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.183.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.184.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.185.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.186.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.187.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.188.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.189.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.190.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.236.191.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.0.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.16.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.32.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.48.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.64.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.80.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.96.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.112.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.128.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.192.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.208.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.224.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.237.240.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.0.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.0.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.16.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.48.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.64.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.80.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.96.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.112.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.128.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.144.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.160.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.176.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.192.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.208.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.224.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.238.240.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.0.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.1.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.2.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.2.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.3.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.4.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.4.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.5.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.6.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.7.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.8.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.9.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.10.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.12.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.16.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.32.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.48.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.64.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.80.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.96.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.112.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.128.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.144.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.160.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.176.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.192.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.208.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.224.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 154.239.240.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 155.12.80.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.86.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.88.0/21 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.88.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.96.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.100.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.106.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.108.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.12.114.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SL71-AFRINIC [Simbanet (T) Limited] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 155.234.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SABC1-AFRINIC [South African Broadcasting Corporation] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 155.235.64.0/19 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.235.96.0/19 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.235.224.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.235.225.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.235.226.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.235.227.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.235.232.0/21 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.235.240.0/22 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM1-AFRINIC [African Oxygen Limited] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 155.237.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA58-AFRINIC [Sasol South Africa (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 155.238.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CT2-AFRINIC [Cape Technikon] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 155.238.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CT2-AFRINIC [Cape Technikon] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 155.238.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CT2-AFRINIC [Cape Technikon] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 155.240.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ82-AFRINIC [Agricultural Research Council] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 155.240.0.0/17 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ82-AFRINIC [Agricultural Research Council] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 155.240.152.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ82-AFRINIC [Agricultural Research Council] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 155.240.160.0/19 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ82-AFRINIC [Agricultural Research Council] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 155.240.192.0/19 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ82-AFRINIC [Agricultural Research Council] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 155.240.224.0/19 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ82-AFRINIC [Agricultural Research Council] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 156.0.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 156.0.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32708] Prefix was owned by ORG-RTOS1-AFRINIC [Root Technologies Of SA (PTY) LTD] Route 156.0.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-VGPL2-AFRINIC [Verdana Group Pty Ltd] Route 156.0.95.0/24 [AS328543] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VGPL2-AFRINIC [Verdana Group Pty Ltd] but owned by ORG-SNCL1-AFRINIC [Sun Network Company Limited] Route 156.0.196.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65201] Prefix was owned by ORG-FRGL1-AFRINIC [Foschini Retail Group (Pty) Ltd] Route 156.0.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65201] Prefix was owned by ORG-FRGL1-AFRINIC [Foschini Retail Group (Pty) Ltd] Route 156.0.200.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23961] Prefix was owned by ORG-XL1-AFRINIC [xTom Limited] Route 156.0.202.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23961] Prefix was owned by ORG-XL1-AFRINIC [xTom Limited] Route 156.8.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL17-AFRINIC [ArcelorMittal South Africa Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 156.38.16.0/20 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.16.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.17.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.18.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.19.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.20.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.21.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.22.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.23.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.24.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.25.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.26.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.27.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.28.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.29.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.30.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.31.0/24 [AS37678] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VS1-AFRINIC [VBN Services] but owned by ORG-BFNL1-AFRINIC [BOTSWANA FIBRE NETWORKS (Proprietary) Limited] Route 156.38.64.0/19 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GT7-AFRINIC [GVA Togo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 156.155.0.0/16 [AS37611] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-AS7-AFRINIC [AFRIHOST SP (PTY) LTD] Route 156.155.248.0/24 [AS328020] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-GS1-AFRINIC [Gardale Solutions] Route 156.155.249.0/24 [AS328020] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-GS1-AFRINIC [Gardale Solutions] Route 156.155.250.0/23 [AS327979] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-DC1-AFRINIC [DIAMATRIX C.C] Route 156.155.250.0/24 [AS327979] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-DC1-AFRINIC [DIAMATRIX C.C] Route 156.155.251.0/24 [AS327979] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-DC1-AFRINIC [DIAMATRIX C.C] Route 156.155.252.0/23 [AS327979] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-DC1-AFRINIC [DIAMATRIX C.C] Route 156.155.252.0/24 [AS327979] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-DC1-AFRINIC [DIAMATRIX C.C] Route 156.155.253.0/24 [AS327979] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-DC1-AFRINIC [DIAMATRIX C.C] Route 156.192.0.0/11 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.192.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.192.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.192.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.192.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.192.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.192.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.193.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.193.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.193.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.193.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.194.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.195.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.196.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.197.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.198.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.199.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.199.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.199.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.199.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.199.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.199.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.200.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.201.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.202.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.203.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.203.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.203.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.203.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.203.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.203.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.203.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.204.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.204.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.204.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.204.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.205.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.205.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.205.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.205.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.206.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.207.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.208.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.208.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.208.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.208.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.209.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.210.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.211.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.211.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.211.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.211.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.211.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.211.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.212.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.213.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.214.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.214.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.214.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.214.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.215.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.215.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.215.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.215.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.217.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.218.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.218.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.218.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.218.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.221.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.222.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.222.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.222.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.222.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.223.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 156.224.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149641] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133929] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55355] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137996] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134365] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.20.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.22.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152705] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210110] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14315] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS14315] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139871] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.224.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137406] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55355] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17497] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214016] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209968] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18301] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133748] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.50.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397423] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19969] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24875] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141718] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214590] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.74.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140869] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18004] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18004] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149641] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4760] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18779] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.225.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.2.0/24 [AS328722] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-CIL6-AFRINIC [Ciudad Infrastructure Limited] Route 156.226.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149628] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11404] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.168.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.170.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134365] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.208.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.218.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.226.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135293] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135293] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS215071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4766] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45102] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.22.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398478] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS394432] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.194.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.204.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.227.208.0/21 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.227.208.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.227.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.224.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.228.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.230.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.246.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS263681] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.227.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3257] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS32043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS31898] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.228.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214025] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17497] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.34.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.44.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213642] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63139] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.66.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.68.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.72.0/21 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.96.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.100.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.101.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.102.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.103.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.104.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.105.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.106.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.107.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.108.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.109.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.110.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.111.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.112.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS12849] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.122.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.128.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.132.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.136.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.138.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.140.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.142.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.144.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.146.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.148.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.150.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.152.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.154.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.156.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.158.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.172.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.229.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.228.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.230.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.232.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.234.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57043] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44901] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.229.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140570] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140570] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140570] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142132] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142132] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131618] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151206] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140475] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141109] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150150] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.230.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400463] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.108.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44509] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.116.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142132] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142132] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.140.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401615] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211265] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.231.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.88.0/24 [AS329278] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-TCL4-AFRINIC [Truehost Cloud Limited] Route 156.232.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS216050] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273478] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.232.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211961] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS197450] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62240] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140951] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30781] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.206.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141159] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.233.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136800] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.114.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS216047] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS216047] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.234.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS274728] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23520] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23520] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272018] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS272018] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.104.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.120.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.235.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136442] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136442] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18046] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45102] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135419] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136970] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142403] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138152] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149440] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16437] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16437] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS16437] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138965] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149014] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149014] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149014] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149014] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.236.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138195] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.96.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.104.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152920] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.237.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134548] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133712] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46071] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.18.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131471] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38193] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24435] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24435] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198247] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134489] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59187] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140925] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50183] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.208.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150313] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150313] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.216.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150313] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150313] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.224.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.228.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.230.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401696] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.248.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.238.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8796] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.32.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134365] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29802] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.156.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152705] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.239.244.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26617] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS26617] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151206] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.64.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.64.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.66.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151206] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151206] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.76.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45102] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142132] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149641] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.80.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141190] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132203] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132203] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.96.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140227] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55967] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.240.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55720] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152179] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132585] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132585] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132585] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214238] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42689] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42689] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153526] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.144.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.176.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.190.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.241.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400463] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4134] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4809] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23764] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131273] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141518] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.64.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.82.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153671] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135377] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.242.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138678] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.128.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214483] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.134.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.243.136.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.243.138.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.243.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.145.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.243.146.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.243.148.0/23 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.243.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS211567] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.176.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.178.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.180.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.184.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.186.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.188.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.243.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.62.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138915] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS19318] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.208.0/24 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 156.244.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.220.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.244.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133115] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135097] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.136.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS17561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.188.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.192.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398704] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS152705] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.242.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.245.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62468] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.4.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136513] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20473] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20326] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36680] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61112] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48031] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202656] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.246.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133007] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139056] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401739] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401739] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64013] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138415] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138648] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.247.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS151407] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64126] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS265721] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS265721] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269816] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.248.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS264750] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138678] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135600] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135386] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139811] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11042] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS54801] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213690] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213690] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213690] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213690] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44559] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140595] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22773] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.124.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS200373] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.192.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.210.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.249.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS131618] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.250.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS35916] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.50.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399077] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213736] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139057] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42689] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.184.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.251.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40065] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23470] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25198] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS273299] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS28458] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138456] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.30.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9294] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398823] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.160.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS394432] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.168.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS394432] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.252.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS213999] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137263] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136907] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41095] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.208.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.210.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.212.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50053] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50053] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7018] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18301] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198584] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.253.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7018] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400619] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS135391] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139923] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.6.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS55933] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214432] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS153706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139880] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62084] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.112.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214143] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.118.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401783] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.124.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS141167] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.126.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132813] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.254.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS142286] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS139646] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212552] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS150706] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3561] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207023] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214413] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS395793] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63888] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.128.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS269984] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.140.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 156.255.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61461] Prefix was owned by ORG-CIL1-AFRINIC [Cloud Innovation Ltd] Route 160.0.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS715] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.0.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.0.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.0.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.0.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS1288] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.0.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS1288] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.0.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS1288] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.0.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 160.116.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.128.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63956] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.116.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-ACSL2-AFRINIC [Affiliated Computing Services (Pty) Ltd] Route 160.119.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7489] Prefix was owned by ORG-HSL1-AFRINIC [HostUS Solutions LLC] Route 160.119.88.0/22 [AS37721] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA65-AFRINIC [1tel S.A.] but owned by ORG-VTS1-AFRINIC [Virtual Technologies & Solutions] Route 160.119.88.0/24 [AS37721] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA65-AFRINIC [1tel S.A.] but owned by ORG-VTS1-AFRINIC [Virtual Technologies & Solutions] Route 160.119.92.0/22 [AS37721] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA65-AFRINIC [1tel S.A.] but owned by ORG-VTS1-AFRINIC [Virtual Technologies & Solutions] Route 160.119.160.0/19 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GGS1-AFRINIC [GVA Gabon SAS] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 160.119.192.0/22 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 160.119.192.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 160.119.193.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 160.119.194.0/24 [AS32437] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ECL7-AFRINIC [Edge connect (pty) Ltd] but owned by ORG-WCTC1-AFRINIC [Webdev CC T/A Cybertek] Route 160.119.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS201942] Prefix was owned by ORG-STI1-AFRINIC [Soltia Telecom INC] Route 160.123.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 160.123.196.0/23 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.198.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.236.0/23 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.236.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.237.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.238.0/23 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.238.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.239.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.240.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.241.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.123.254.0/24 [AS329501] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMIG1-AFRINIC [Old Mutual Investment Group (PTY) Ltd] Route 160.123.255.0/24 [AS328486] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OM1-AFRINIC [Old Mutual] but owned by ORG-OMLA1-AFRINIC [Old Mutual Life Assurance Company (South Africa) Limited] Route 160.124.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.124.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132839] Prefix was owned by ORG-PS1-AFRINIC [Posix Systems (Pty) Ltd] Route 160.224.0.0/15 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.52.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.56.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.96.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.100.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.102.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.108.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.110.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.112.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.114.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.124.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.126.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.128.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.136.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.152.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.166.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.180.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.182.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.184.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.202.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.212.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.216.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.238.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.246.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.248.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.224.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.16.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.20.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.24.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.26.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.28.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.32.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.62.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.68.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.78.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.80.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.82.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.98.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.106.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.108.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.110.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.112.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.114.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.142.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.148.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.150.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.152.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.160.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.162.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.168.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.170.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.182.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.184.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.194.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.196.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.200.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.210.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.216.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.218.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6424] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.238.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.244.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.225.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-AT1-AFRINIC [Angola Telecom] Route 160.226.180.0/22 [AS327688] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL35-AFRINIC [Infraplex (Pty) Ltd] but owned by ORG-GWIt1-AFRINIC [Screamer Telecommunications] Route 160.226.180.0/23 [AS327688] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL35-AFRINIC [Infraplex (Pty) Ltd] but owned by ORG-GWIt1-AFRINIC [Screamer Telecommunications] Route 160.226.182.0/23 [AS327688] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IL35-AFRINIC [Infraplex (Pty) Ltd] but owned by ORG-GWIt1-AFRINIC [Screamer Telecommunications] Route 160.242.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 160.242.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 160.242.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 160.242.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 160.242.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-MDPE1-AFRINIC [MINISTERE DES POSTES ET DE L'ECONOMIE NUMERIQUE] Route 160.242.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-MDPE1-AFRINIC [MINISTERE DES POSTES ET DE L'ECONOMIE NUMERIQUE] Route 160.242.201.0/24 [AS329010] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MDPE1-AFRINIC [MINISTERE DES POSTES ET DE L'ECONOMIE NUMERIQUE] but owned by ORG-SDN1-AFRINIC [Soci??t?? d'Infrastructures Num??riques (SIN)] Route 160.242.202.0/24 [AS329010] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MDPE1-AFRINIC [MINISTERE DES POSTES ET DE L'ECONOMIE NUMERIQUE] but owned by ORG-SDN1-AFRINIC [Soci??t?? d'Infrastructures Num??riques (SIN)] Route 160.242.203.0/24 [AS329010] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MDPE1-AFRINIC [MINISTERE DES POSTES ET DE L'ECONOMIE NUMERIQUE] but owned by ORG-SDN1-AFRINIC [Soci??t?? d'Infrastructures Num??riques (SIN)] Route 161.123.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS136744] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.56.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.70.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.94.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.96.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.112.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.118.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.140.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.148.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203999] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.208.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61290] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50028] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS133499] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61290] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61290] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203020] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 161.123.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS207990] Prefix was owned by ORG-WCL2-AFRINIC [Wirels Connect (PTY) Ltd] Route 163.121.63.0/24 [AS25576] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IA17-AFRINIC [IDSC] but owned by ORG-AA21-AFRINIC [AFMIC] Route 163.121.104.0/24 [AS25576] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IA17-AFRINIC [IDSC] but owned by ORG-AA21-AFRINIC [AFMIC] Route 163.121.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-IA17-AFRINIC [IDSC] Route 163.121.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-IA17-AFRINIC [IDSC] Route 163.121.166.0/24 [AS37112] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IA17-AFRINIC [IDSC] but owned by ORG-DA7-AFRINIC [Dar Al-Handasah] Route 163.195.0.0/17 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CPA1-AFRINIC [Cape Provincial Administration] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 163.195.38.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CPA1-AFRINIC [Cape Provincial Administration] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 163.195.40.0/22 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CPA1-AFRINIC [Cape Provincial Administration] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 163.195.128.0/17 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CPA1-AFRINIC [Cape Provincial Administration] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 163.196.254.0/24 [AS3067] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NSL1-AFRINIC [Nissan S.A. (Pty) Ltd] but owned by ORG-GHL1-AFRINIC [Gijima Holdings (PTY) Limited] Route 163.196.255.0/24 [AS3067] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NSL1-AFRINIC [Nissan S.A. (Pty) Ltd] but owned by ORG-GHL1-AFRINIC [Gijima Holdings (PTY) Limited] Route 163.197.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.197.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62976] Prefix was owned by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] Route 163.198.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.102.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63956] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.160.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.172.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.208.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.198.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AA79-AFRINIC [Agrihold] Route 163.199.84.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8075] Prefix was owned by ORG-NBL1-AFRINIC [Nedbank Limited] Route 163.199.96.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.199.98.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.199.99.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.199.101.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.199.104.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.199.108.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.199.136.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.199.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15404] Prefix was owned by ORG-NBL1-AFRINIC [Nedbank Limited] Route 163.200.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ218-AFRINIC [University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 163.200.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ218-AFRINIC [University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 163.200.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ218-AFRINIC [University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 163.201.225.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 163.201.226.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 163.201.227.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NBL1-AFRINIC [Nedbank Limited] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 163.203.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FSL1-AFRINIC [CoCre8 IT Services (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.203.0.0/18 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FSL1-AFRINIC [CoCre8 IT Services (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.203.64.0/18 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FSL1-AFRINIC [CoCre8 IT Services (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.203.160.0/19 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FSL1-AFRINIC [CoCre8 IT Services (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.203.192.0/19 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FSL1-AFRINIC [CoCre8 IT Services (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 163.203.224.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FSL1-AFRINIC [CoCre8 IT Services (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 164.146.0.0/15 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GoSA1-AFRINIC [Government of South Africa] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 164.148.0.0/14 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GoSA1-AFRINIC [Government of South Africa] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 164.151.0.0/17 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GoSA1-AFRINIC [Government of South Africa] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 164.151.128.0/17 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GoSA1-AFRINIC [Government of South Africa] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 164.155.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.155.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137443] Prefix was owned by ORG-SL72-AFRINIC [Sentrachem Limited] Route 164.160.16.0/22 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GC7-AFRINIC [GVA Congo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 164.160.108.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BISL1-AFRINIC [Bitstream Internet Solutions (Proprietary) Limited] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 164.160.109.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BISL1-AFRINIC [Bitstream Internet Solutions (Proprietary) Limited] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 164.160.110.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BISL1-AFRINIC [Bitstream Internet Solutions (Proprietary) Limited] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 164.160.111.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BISL1-AFRINIC [Bitstream Internet Solutions (Proprietary) Limited] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 164.160.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-IL28-AFRINIC [123 Internetworks (Pty) Ltd] Route 164.160.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-IL28-AFRINIC [123 Internetworks (Pty) Ltd] Route 164.160.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-IL28-AFRINIC [123 Internetworks (Pty) Ltd] Route 164.160.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-IL28-AFRINIC [123 Internetworks (Pty) Ltd] Route 164.160.184.0/24 [AS24757] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WISP1-AFRINIC [WebSprix IT Solution PLC] but owned by ORG-ETC2-AFRINIC [Ethio Telecom] Route 164.160.185.0/24 [AS24757] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WISP1-AFRINIC [WebSprix IT Solution PLC] but owned by ORG-ETC2-AFRINIC [Ethio Telecom] Route 164.160.186.0/24 [AS24757] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WISP1-AFRINIC [WebSprix IT Solution PLC] but owned by ORG-ETC2-AFRINIC [Ethio Telecom] Route 164.160.187.0/24 [AS24757] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WISP1-AFRINIC [WebSprix IT Solution PLC] but owned by ORG-ETC2-AFRINIC [Ethio Telecom] Route 164.160.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21351] Prefix was owned by ORG-NO3-AFRINIC [NET OI] Route 165.3.0.0/16 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.3.0.0/18 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.3.64.0/18 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.4.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.6.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.7.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.10.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.11.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.12.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.12.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.14.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.15.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.20.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.4.22.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 165.5.0.0/23 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.5.2.0/23 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.5.6.0/23 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.5.7.0/24 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.5.12.0/23 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.5.14.0/23 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.5.20.0/24 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.5.22.0/24 [AS327839] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA1-AFRINIC [Woolworths Holdings Limited] but owned by ORG-WL5-AFRINIC [Woolworths(Proprietary) Ltd] Route 165.8.0.0/16 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SAPO1-AFRINIC [South African Post Office] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 165.9.0.0/16 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SAPO1-AFRINIC [South African Post Office] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 165.10.0.0/16 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SAPO1-AFRINIC [South African Post Office] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 165.11.0.0/16 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SAPO1-AFRINIC [South African Post Office] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 165.49.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202736] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209181] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49608] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS154049] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214432] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49608] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.83.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA5-AFRINIC [Wirulink Pty Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 165.49.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49608] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS393942] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3320] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214432] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6079] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49608] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5650] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214432] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63199] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.215.0/24 [AS329386] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WA5-AFRINIC [Wirulink Pty Ltd] but owned by ORG-NC8-AFRINIC [Neurotel Communications] Route 165.49.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214572] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205886] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS984] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.49.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5511] Prefix was owned by ORG-WA5-AFRINIC [Wirulink Pty Ltd] Route 165.73.186.0/24 [AS329300] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-HP1-AFRINIC [HERO TELECOMS (PTY) LTD] but owned by ORG-VL11-AFRINIC [HEROTEL BUSINESS (PTY) LTD] Route 165.73.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.73.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-PNZ1-AFRINIC [Psychz Networks ZA] Route 165.90.64.0/19 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.64.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.65.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.66.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.67.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.68.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.69.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.70.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.71.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.72.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.73.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.74.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.75.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.76.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.77.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.78.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.79.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.80.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.81.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.82.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.83.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.84.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.85.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.86.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.87.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.88.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.89.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.90.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.91.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.92.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.93.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.94.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.90.95.0/24 [AS37110] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 165.148.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64512] Prefix was owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 165.148.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64512] Prefix was owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 165.231.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205056] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.40.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 165.231.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 168.76.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS140224] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.76.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137951] Prefix was owned by ORG-FSED1-AFRINIC [Free State Education Department] Route 168.80.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45671] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45671] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63018] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS202769] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44066] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.80.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.132.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.200.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.232.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.240.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.80.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137409] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.8.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137409] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS137409] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.16.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.40.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.42.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38001] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63018] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.136.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.188.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.196.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.212.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.218.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11990] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.236.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.244.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS132335] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.81.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203833] Prefix was owned by ORG-AISL1-AFRINIC [AECI Information Services (Pty) Ltd] Route 168.89.0.0/16 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JCC1-AFRINIC [Johannesburg City Council] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 168.128.134.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS27435] Prefix was owned by ORG-DD1-AFRINIC [Dimension Data] Route 168.155.16.0/24 [AS37314] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA60-AFRINIC [SAPPI] but owned by ORG-SI4-AFRINIC [Inq Digital South Africa (Pty) Ltd] Route 168.172.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.0.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.1.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.20.0/22 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.24.0/21 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.41.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.43.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.47.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.48.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.64.0/18 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.87.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.88.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.89.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.93.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.94.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.95.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.109.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.129.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.130.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.131.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.132.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.133.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.134.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.136.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.137.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.138.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.140.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.142.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.143.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.144.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.145.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.147.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.150.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.151.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.152.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.153.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.154.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.155.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.160.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.161.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.162.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.164.0/22 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.168.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.170.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.174.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.176.0/20 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.193.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.194.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.196.0/22 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.200.0/21 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.208.0/22 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.212.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.224.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.225.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.230.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.232.0/21 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.240.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.243.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.251.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.172.252.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TP1-AFRINIC [Tshwane University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 168.210.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS18775] Prefix was owned by ORG-DD1-AFRINIC [Dimension Data] Route 168.253.0.0/20 [AS37410] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CLI2-AFRINIC [NOVAFONE Inc] but owned by ORG-LCC1-AFRINIC [Lonestar Communications Corporation] Route 168.253.1.0/24 [AS37410] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CLI2-AFRINIC [NOVAFONE Inc] but owned by ORG-LCC1-AFRINIC [Lonestar Communications Corporation] Route 168.253.2.0/24 [AS37410] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CLI2-AFRINIC [NOVAFONE Inc] but owned by ORG-LCC1-AFRINIC [Lonestar Communications Corporation] Route 168.253.24.0/24 [AS37410] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CLI2-AFRINIC [NOVAFONE Inc] but owned by ORG-LCC1-AFRINIC [Lonestar Communications Corporation] Route 168.253.44.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-CABS1-AFRINIC [YoAfrica (Pvt) Ltd] Route 168.253.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS206283] Prefix was owned by ORG-CABS1-AFRINIC [YoAfrica (Pvt) Ltd] Route 168.253.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49902] Prefix was owned by ORG-SRdR1-AFRINIC [Societe Reunionnaise du Radiotelephone] Route 169.129.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-SA58-AFRINIC [Sasol South Africa (PTY) LTD] Route 169.129.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-SA58-AFRINIC [Sasol South Africa (PTY) LTD] Route 169.129.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-SA58-AFRINIC [Sasol South Africa (PTY) LTD] Route 169.129.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21859] Prefix was owned by ORG-SA58-AFRINIC [Sasol South Africa (PTY) LTD] Route 169.159.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3356] Prefix was owned by ORG-LCSA1-AFRINIC [Centurylink Communications South Africa Pty Ltd] Route 169.159.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3356] Prefix was owned by ORG-LCSA1-AFRINIC [Centurylink Communications South Africa Pty Ltd] Route 169.159.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3356] Prefix was owned by ORG-LCSA1-AFRINIC [Centurylink Communications South Africa Pty Ltd] Route 169.202.201.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ABSA1-AFRINIC [ABSA (Amalgamated Banks of South Africa)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 169.202.202.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ABSA1-AFRINIC [ABSA (Amalgamated Banks of South Africa)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 169.239.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-ATS3-AFRINIC [AVS TELECOM SARL] Route 169.239.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-ATS3-AFRINIC [AVS TELECOM SARL] Route 169.239.104.0/22 [AS30619] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IIoI1-AFRINIC [INTIC (National Institute of ICT)] but owned by ORG-TMTS1-AFRINIC [TMCEL - Mo??ambique Telecom, SA] Route 169.239.112.0/22 [AS37529] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CNPI1-AFRINIC [Centro Nacional para Informatizacion de la Administracion Publica] but owned by ORG-GdId1-AFRINIC [Gestora de Infraestructuras de Telecomunicaciones de Guinea Ecuatorial] Route 169.239.116.0/22 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AINA1-AFRINIC [Alriyada Internet Networking and DVB Services LLC] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 169.239.116.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AINA1-AFRINIC [Alriyada Internet Networking and DVB Services LLC] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 169.239.117.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AINA1-AFRINIC [Alriyada Internet Networking and DVB Services LLC] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 169.239.119.0/24 [AS37284] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AINA1-AFRINIC [Alriyada Internet Networking and DVB Services LLC] but owned by ORG-AAFT1-AFRINIC [Aljeel Aljadeed For Technology] Route 169.239.128.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61138] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.130.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61138] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS49870] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138995] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-HS1-AFRINIC [HAYO SA] Route 169.239.137.0/24 [AS37196] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-HS1-AFRINIC [HAYO SA] but owned by ORG-SS1-AFRINIC [Sudatel Senegal] Route 169.239.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS31167] Prefix was owned by ORG-AGS6-AFRINIC [AXIONE Gabon SA] Route 169.239.152.0/22 [AS37153] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AL7-AFRINIC [AfriVPN Ltd] but owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 169.239.184.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29606] Prefix was owned by ORG-BC5-AFRINIC [Borwood Communications (Pty) Ltd] Route 169.239.188.0/22 [AS37613] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EISL2-AFRINIC [ETG Integrated Services Ltd] but owned by ORG-EISL1-AFRINIC [DOLPHIN TELECOMMUNICATION LIMITED] Route 169.239.188.0/24 [AS37613] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EISL2-AFRINIC [ETG Integrated Services Ltd] but owned by ORG-EISL1-AFRINIC [DOLPHIN TELECOMMUNICATION LIMITED] Route 169.239.189.0/24 [AS37613] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EISL2-AFRINIC [ETG Integrated Services Ltd] but owned by ORG-EISL1-AFRINIC [DOLPHIN TELECOMMUNICATION LIMITED] Route 169.239.196.0/24 [AS329109] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DS3-AFRINIC [DIAKEMINVESTMENT SL] but owned by ORG-ZL5-AFRINIC [Zoodlabs(SL) Limited] Route 169.239.197.0/24 [AS329109] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DS3-AFRINIC [DIAKEMINVESTMENT SL] but owned by ORG-ZL5-AFRINIC [Zoodlabs(SL) Limited] Route 169.239.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209049] Prefix was owned by ORG-DS3-AFRINIC [DIAKEMINVESTMENT SL] Route 169.239.199.0/24 [AS329109] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DS3-AFRINIC [DIAKEMINVESTMENT SL] but owned by ORG-ZL5-AFRINIC [Zoodlabs(SL) Limited] Route 169.239.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203061] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203061] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS204136] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203061] Prefix was owned by ORG-ZAL1-AFRINIC [Zappie Africa LTD] Route 169.239.204.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13886] Prefix was owned by ORG-MSTL3-AFRINIC [Megabit Servers Technologies LTD] Route 169.239.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7029] Prefix was owned by ORG-MSTL3-AFRINIC [Megabit Servers Technologies LTD] Route 169.239.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397373] Prefix was owned by ORG-MSTL3-AFRINIC [Megabit Servers Technologies LTD] Route 169.239.224.0/22 [AS37153] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DA9-AFRINIC [Datasync] but owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 169.255.32.0/24 [AS328446] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] but owned by ORG-OATL1-AFRINIC [Open Access Technologies (Pty) Ltd] Route 169.255.33.0/24 [AS328446] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] but owned by ORG-OATL1-AFRINIC [Open Access Technologies (Pty) Ltd] Route 169.255.34.0/24 [AS328446] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] but owned by ORG-OATL1-AFRINIC [Open Access Technologies (Pty) Ltd] Route 169.255.35.0/24 [AS328446] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LA3-AFRINIC [The Cloud Crew (Pty) Ltd] but owned by ORG-OATL1-AFRINIC [Open Access Technologies (Pty) Ltd] Route 169.255.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-IL28-AFRINIC [123 Internetworks (Pty) Ltd] Route 169.255.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-IL28-AFRINIC [123 Internetworks (Pty) Ltd] Route 169.255.38.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61092] Prefix was owned by ORG-IL28-AFRINIC [123 Internetworks (Pty) Ltd] Route 169.255.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-OS3-AFRINIC [Orioncom SPRL] Route 192.33.10.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NAC1-AFRINIC [iThemba LABS] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.70.200.0/24 [AS37314] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-APSA1-AFRINIC [Air Products South Africa (Pty) Ltd] but owned by ORG-SI4-AFRINIC [Inq Digital South Africa (Pty) Ltd] Route 192.94.61.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ147-AFRINIC [Medical University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.94.210.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TSAM1-AFRINIC [The South African Medical Research Council] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.1.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ6-AFRINIC [ELSENBERG] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.2.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ218-AFRINIC [University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.5.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ125-AFRINIC [Hartebeesthoek Radio Astronomy Observatory] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.7.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.8.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.15.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.20.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ220-AFRINIC [University of Transkei] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.21.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ214-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.22.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CT4-AFRINIC [CEQURUX TECHNOLOGIES] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.38.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ68-AFRINIC [Onderstepoort Veterinary Institute] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.46.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ64-AFRINIC [Kohler Packaging Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.57.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ31-AFRINIC [Grinaker Computing Services] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.88.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ43-AFRINIC [Compustat (Pty) Ltd] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 192.96.89.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ42-AFRINIC [Paradigm Systems Technology] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.92.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ42-AFRINIC [Paradigm Systems Technology] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.96.0/24 [AS37153] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ38-AFRINIC [Roodepoort City Council] but owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 192.96.109.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ35-AFRINIC [South African Astronomical Observatory] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.132.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ31-AFRINIC [Grinaker Computing Services] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.133.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ31-AFRINIC [Grinaker Computing Services] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.134.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ27-AFRINIC [S.A. Warehousing Services] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.139.0/24 [AS37315] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ30-AFRINIC [SQL Integrators (Pty) Ltd] but owned by ORG-CA6-AFRINIC [Cipherwave] Route 192.96.140.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.141.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.142.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.193.0/24 [AS327701] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ14-AFRINIC [Sabinet Online Ltd] but owned by ORG-SG3-AFRINIC [Sabinet Gateway] Route 192.96.234.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.235.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.236.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.237.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.238.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.239.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.240.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.241.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.242.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.243.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 192.96.247.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.250.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.96.251.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ4-AFRINIC [Synergy Computing (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 192.96.252.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ3-AFRINIC [Technikon Witwatersrand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.102.9.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ224-AFRINIC [University of the Western Cape] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 192.136.55.0/24 [AS25543] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OA1-AFRINIC [ORSTOM] but owned by ORG-ONdT1-AFRINIC [ONATEL (Office National des Telecommunications, PTT)] Route 192.142.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6206] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6206] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6206] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44259] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210636] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210636] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210636] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60064] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS210636] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214120] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS398256] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44259] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44259] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.142.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS214036] Prefix was owned by ORG-XNS1-AFRINIC [X-DSL Networking Solutions] Route 192.143.0.0/16 [AS37611] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ADL1-AFRINIC [Axxess DSL (PTY) Ltd] but owned by ORG-AS7-AFRINIC [AFRIHOST SP (PTY) LTD] Route 193.95.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.0.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.3.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.8.0/23 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 193.95.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.16.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.22.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.30.0/23 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 193.95.33.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 193.95.34.0/23 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 193.95.34.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 193.95.36.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 193.95.38.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 193.95.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.42.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.44.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.51.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 193.95.53.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.54.0/23 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.57.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.59.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.65.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 193.95.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.70.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.73.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.75.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.76.0/23 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.78.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.79.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.80.0/23 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.82.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.83.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.88.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.92.0/23 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.95.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.99.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 193.95.105.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.107.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.110.0/23 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.112.0/21 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.115.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 193.95.121.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.122.0/23 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.95.124.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 193.189.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11355] Prefix was owned by ORG-SPDC1-AFRINIC [Shell Petroleum Development Company of Nigeria] Route 193.189.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS11355] Prefix was owned by ORG-SPDC1-AFRINIC [Shell Petroleum Development Company of Nigeria] Route 193.194.50.0/24 [AS6713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AU1-AFRINIC [Al'Akhawayn University] but owned by ORG-ONdP1-AFRINIC [Office National des Postes et Telecommunications ONPT (Maroc Telecom) / IAM] Route 193.227.50.0/23 [AS328762] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EUN1-AFRINIC [Egyptian Universities Network (EUN)] but owned by ORG-MU4-AFRINIC [Mansoura University] Route 194.79.96.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 194.79.96.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 194.79.103.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 194.79.108.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 194.79.116.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 194.79.119.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 195.202.64.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.64.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.65.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.66.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.67.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.72.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.73.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.75.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.76.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.80.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.80.0/22 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.81.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.87.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.88.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.88.0/22 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.88.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.89.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.90.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.92.0/22 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 195.202.93.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.0.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.85.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.0.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.0.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS21491] Prefix was owned by ORG-UTL1-AFRINIC [Uganda Telecom Ltd] Route 196.1.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-UA3-AFRINIC [Universite-Dakar] Route 196.1.115.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DEV1-AFRINIC [Techdynamics (Pvt) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.2.2.0/24 [AS14988] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UoB1-AFRINIC [University of Botswana] but owned by ORG-BTC2-AFRINIC [Botswana Telecommunications Corporation] Route 196.2.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.12.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.14.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25429] Prefix was owned by ORG-CS2-AFRINIC [Centre Burundais de l'Internet (CBINET SA)] Route 196.2.64.0/20 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.64.0/21 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.64.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.66.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.67.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.68.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.69.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.70.0/23 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.70.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.72.0/21 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.72.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.73.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.75.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.76.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.2.79.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.3.105.0/24 [AS11845] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FCL1-AFRINIC [Flight Centre Travel Group (PTY) Ltd] but owned by ORG-DPBO1-AFRINIC [Vox Telecom Ltd] Route 196.3.110.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ61-AFRINIC [Lennon Ltd] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.3.113.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ176-AFRINIC [NetConnect cc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.3.114.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ176-AFRINIC [NetConnect cc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.3.115.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ176-AFRINIC [NetConnect cc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.3.151.0/24 [AS11157] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 196.3.155.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JOCc1-AFRINIC [Jack Online Communication cc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.3.156.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CAMA1-AFRINIC [Coronation Asset Management (South Africa)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.3.159.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CAMA1-AFRINIC [Coronation Asset Management (South Africa)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.3.161.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DS1-AFRINIC [DynaMique Systems] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.3.163.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LSL1-AFRINIC [Lear Seating (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.30.0/23 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IfMT1-AFRINIC [Armscor Business PTY LTD] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.32.0/22 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IfMT1-AFRINIC [Armscor Business PTY LTD] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.71.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ175-AFRINIC [Price Forbes] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.72.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ175-AFRINIC [Price Forbes] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.76.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MPD1-AFRINIC [Micro & Peripheral Distributors] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.83.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EAWS1-AFRINIC [Europ Assistance Worldwide Services] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.84.0/24 [AS327701] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ14-AFRINIC [Sabinet Online Ltd] but owned by ORG-SG3-AFRINIC [Sabinet Gateway] Route 196.4.95.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BT1-AFRINIC [Border Technikon] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.4.97.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AC1-AFRINIC [ABS Computers] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.100.0/22 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.104.0/22 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.140.0/23 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.142.0/23 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.143.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.144.0/22 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.145.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.146.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.147.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.148.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA75-AFRINIC [ARMSCOR] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.4.163.0/24 [AS37028] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ191-AFRINIC [Momentum Investments Shared Services(Pty) Ltd] but owned by ORG-FRBL1-AFRINIC [First Rand Bank Limited] Route 196.4.164.0/24 [AS37028] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ191-AFRINIC [Momentum Investments Shared Services(Pty) Ltd] but owned by ORG-FRBL1-AFRINIC [First Rand Bank Limited] Route 196.4.165.0/24 [AS37028] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ191-AFRINIC [Momentum Investments Shared Services(Pty) Ltd] but owned by ORG-FRBL1-AFRINIC [First Rand Bank Limited] Route 196.4.168.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ182-AFRINIC [BMW (SA) (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.172.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DA3-AFRINIC [Data Abstraction] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.173.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCS2-AFRINIC [CHEP SOUTH AFRICA (Proprietary) LIMITED] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.174.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCS2-AFRINIC [CHEP SOUTH AFRICA (Proprietary) LIMITED] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.175.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCS2-AFRINIC [CHEP SOUTH AFRICA (Proprietary) LIMITED] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.4.176.0/21 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCS2-AFRINIC [CHEP SOUTH AFRICA (Proprietary) LIMITED] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.176.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCS2-AFRINIC [CHEP SOUTH AFRICA (Proprietary) LIMITED] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.4.184.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCS2-AFRINIC [CHEP SOUTH AFRICA (Proprietary) LIMITED] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.188.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GCS2-AFRINIC [CHEP SOUTH AFRICA (Proprietary) LIMITED] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.212.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ158-AFRINIC [National Brands Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.216.0/21 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ158-AFRINIC [National Brands Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.224.0/21 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ158-AFRINIC [National Brands Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.4.255.0/24 [AS33567] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CBoL1-AFRINIC [Central Bank of Lesotho] but owned by ORG-TLL1-AFRINIC [Econet Telecom Lesotho (PTY) LTD] Route 196.6.133.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.136.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.137.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.141.0/24 [AS37457] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.6.142.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.143.0/24 [AS37457] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.6.147.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.149.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.150.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.151.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.153.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.160.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.161.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.162.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.165.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.167.0/24 [AS37457] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.6.170.0/24 [AS37100] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-SL75-AFRINIC [SEACOM Limited] Route 196.6.171.0/24 [AS37100] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-SL75-AFRINIC [SEACOM Limited] Route 196.6.172.0/24 [AS37100] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AFG1-AFRINIC [Alexander Forbes Group Inc] but owned by ORG-SL75-AFRINIC [SEACOM Limited] Route 196.6.198.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ195-AFRINIC [National Library of S.A] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.6.212.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ233-AFRINIC [GIMS (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.212.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ233-AFRINIC [GIMS (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.221.0/24 [AS8094] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ223-AFRINIC [University of the North West] but owned by ORG-PU1-AFRINIC [North West University] Route 196.6.222.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ234-AFRINIC [Mintek] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.237.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ235-AFRINIC [Pretoria Portland Cement] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.6.243.0/24 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CBL1-AFRINIC [CAPITEC BANK LIMITED] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 196.6.251.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FSL1-AFRINIC [CoCre8 IT Services (PTY) LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.7.93.0/24 [AS37353] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VSA1-AFRINIC [MTN SA] but owned by ORG-MC6-AFRINIC [Seacom Western Cape (Pty) Ltd] Route 196.7.127.0/24 [AS37353] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VSA1-AFRINIC [MTN SA] but owned by ORG-MC6-AFRINIC [Seacom Western Cape (Pty) Ltd] Route 196.8.153.0/24 [AS328003] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TSBO2-AFRINIC [The Standard Bank of South Africa (Proprietary) Limited] but owned by ORG-STCS1-AFRINIC [STANDARD TELECOM CONGO SARL- STC SA] Route 196.8.224.0/24 [AS37447] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TSBO2-AFRINIC [The Standard Bank of South Africa (Proprietary) Limited] but owned by ORG-CCTs2-AFRINIC [ORANGE RDC] Route 196.8.225.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TSBO2-AFRINIC [The Standard Bank of South Africa (Proprietary) Limited] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.8.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65235] Prefix was owned by ORG-TSBO2-AFRINIC [The Standard Bank of South Africa (Proprietary) Limited] Route 196.10.88.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138527] Prefix was owned by ORG-ZZ154-AFRINIC [Nampak Management Services] Route 196.10.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138527] Prefix was owned by ORG-ZZ154-AFRINIC [Nampak Management Services] Route 196.10.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138527] Prefix was owned by ORG-ZZ154-AFRINIC [Nampak Management Services] Route 196.10.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138527] Prefix was owned by ORG-ZZ154-AFRINIC [Nampak Management Services] Route 196.10.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS138527] Prefix was owned by ORG-ZZ154-AFRINIC [Nampak Management Services] Route 196.10.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13444] Prefix was owned by ORG-ZZ154-AFRINIC [Nampak Management Services] Route 196.10.101.0/24 [AS12091] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ192-AFRINIC [Mobile Telephone Network] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.10.104.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ84-AFRINIC [Astec Communications (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.118.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ96-AFRINIC [Cellular Operations (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.121.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ217-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.10.124.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ88-AFRINIC [Anglovaal Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.130.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ124-AFRINIC [Guardian National] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.132.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ124-AFRINIC [Guardian National] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.150.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ201-AFRINIC [Simera Pty (Ltd)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.152.0/21 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ201-AFRINIC [Simera Pty (Ltd)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.160.0/19 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ201-AFRINIC [Simera Pty (Ltd)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.192.0/21 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ201-AFRINIC [Simera Pty (Ltd)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.203.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.10.204.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ128-AFRINIC [IGI Life] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.208.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ128-AFRINIC [IGI Life] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.212.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ128-AFRINIC [IGI Life] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.216.0/22 [AS21271] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AdTd1-AFRINIC [Agence des Technologies de lnformation et de la Communication (AGETIC)] but owned by ORG-SoMT1-AFRINIC [Society of Mali's Telecommunications (SOTELMA)] Route 196.10.216.0/24 [AS21271] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AdTd1-AFRINIC [Agence des Technologies de lnformation et de la Communication (AGETIC)] but owned by ORG-SoMT1-AFRINIC [Society of Mali's Telecommunications (SOTELMA)] Route 196.10.220.0/24 [AS30985] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AdTd1-AFRINIC [Agence des Technologies de lnformation et de la Communication (AGETIC)] but owned by ORG-IS28-AFRINIC [Orange Mali SA] Route 196.10.221.0/24 [AS30985] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AdTd1-AFRINIC [Agence des Technologies de lnformation et de la Communication (AGETIC)] but owned by ORG-IS28-AFRINIC [Orange Mali SA] Route 196.10.224.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ176-AFRINIC [NetConnect cc] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.10.229.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ169-AFRINIC [Open Systems Integrators] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.248.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EAWS1-AFRINIC [Europ Assistance Worldwide Services] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.10.249.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EAWS1-AFRINIC [Europ Assistance Worldwide Services] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.1.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.2.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.3.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.4.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.5.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.6.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.7.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.8.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.9.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.10.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.11.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.12.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.13.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.14.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.15.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.16.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.17.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.18.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.19.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.20.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.21.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.22.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.23.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.24.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.25.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.26.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.28.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.30.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ75-AFRINIC [Airports Company Limited] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.11.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64437] Prefix was owned by ORG-eEB1-AFRINIC [Sanlam Life Insurance Limited] Route 196.11.56.0/23 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ192-AFRINIC [Mobile Telephone Network] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.11.58.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VA67-AFRINIC [Vodacom] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.69.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ89-AFRINIC [Allianz Insurance] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.70.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ89-AFRINIC [Allianz Insurance] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.72.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ89-AFRINIC [Allianz Insurance] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.76.0/22 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UoS2-AFRINIC [University of Stellenbosch] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.98.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ224-AFRINIC [University of the Western Cape] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.109.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ184-AFRINIC [QNet (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.110.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ184-AFRINIC [QNet (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.112.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ184-AFRINIC [QNet (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.114.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ184-AFRINIC [QNet (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.116.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ126-AFRINIC [Hill Cunnington & Associates] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.122.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ111-AFRINIC [East London Credit Bureau] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.136.0/22 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ225-AFRINIC [University of Zululand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.136.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ225-AFRINIC [University of Zululand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.138.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ225-AFRINIC [University of Zululand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.140.0/22 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ225-AFRINIC [University of Zululand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.140.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ225-AFRINIC [University of Zululand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.142.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ225-AFRINIC [University of Zululand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.11.148.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VA67-AFRINIC [Vodacom] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.152.0/21 [AS37353] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TSI1-AFRINIC [SEACOM KZN (Pty) Ltd] but owned by ORG-MC6-AFRINIC [Seacom Western Cape (Pty) Ltd] Route 196.11.170.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.172.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.174.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.175.0/24 [AS37057] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LNIC1-AFRINIC [Lesotho Network Information Centre Proprietary] but owned by ORG-VLL1-AFRINIC [Vodacom Lesotho (Pty) Ltd] Route 196.11.188.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ151-AFRINIC [Mosaic Software (UK) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.192.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.11.193.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.11.194.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.11.195.0/24 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 196.11.196.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ87-AFRINIC [Avitronics] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.11.197.0/24 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ191-AFRINIC [Momentum Investments Shared Services(Pty) Ltd] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 196.11.205.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ131-AFRINIC [IO Systems Corporation] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.209.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ107-AFRINIC [Digitron Information Technologies] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.11.235.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ224-AFRINIC [University of the Western Cape] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.12.128.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.129.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.130.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.131.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.132.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.134.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.135.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.137.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.138.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.139.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.140.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.143.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.144.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.145.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.146.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.147.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.148.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.149.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.150.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.151.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.152.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.153.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.154.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.155.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.156.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.158.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.159.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.12.203.0/24 [AS30983] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MC5-AFRINIC [Wana Corporate] but owned by ORG-CNpl1-AFRINIC [CNRST (Centre National pour la Recherche Scientifique et Technique)] Route 196.13.35.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.63.0/24 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 196.13.70.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.13.72.0/24 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 196.13.73.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.74.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.76.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.78.0/24 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 196.13.79.0/24 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.13.80.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DTSA2-AFRINIC [DXC Technology South Africa (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.93.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ161-AFRINIC [Cybersoft] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.97.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ161-AFRINIC [Cybersoft] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.113.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ187-AFRINIC [RTT] but owned by ORG-VA67-AFRINIC [Vodacom] Route 196.13.115.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.116.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.117.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.118.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.119.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.127.0/24 [AS37630] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ237-AFRINIC [Ernest & Young] but owned by ORG-EA27-AFRINIC [Ernst and Young Services Limited] Route 196.13.129.0/24 [AS37630] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ237-AFRINIC [Ernest & Young] but owned by ORG-EA27-AFRINIC [Ernst and Young Services Limited] Route 196.13.130.0/24 [AS37630] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ237-AFRINIC [Ernest & Young] but owned by ORG-EA27-AFRINIC [Ernst and Young Services Limited] Route 196.13.131.0/24 [AS37630] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ237-AFRINIC [Ernest & Young] but owned by ORG-EA27-AFRINIC [Ernst and Young Services Limited] Route 196.13.132.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ172-AFRINIC [Universitas Hospital] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.150.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ220-AFRINIC [University of Transkei] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.163.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ123-AFRINIC [Glenvaal Dewar Rand] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.164.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ153-AFRINIC [Mutual and Federal] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.165.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ8-AFRINIC [Columbus Stainless (Proprietary) Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.185.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ222-AFRINIC [University of Venda] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.187.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ147-AFRINIC [Medical University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.188.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ147-AFRINIC [Medical University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.190.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ147-AFRINIC [Medical University of South Africa] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.200.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ141-AFRINIC [Technikon Mangosuthu aka Mangosuthu University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.13.213.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ221-AFRINIC [Unitrans Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.214.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ238-AFRINIC [Unitrans Hosting] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.216.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ239-AFRINIC [International Healthcate Distributors (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.225.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ230-AFRINIC [Momentum Life] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.232.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ171-AFRINIC [Hirt and Carter Cape (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-CBL1-AFRINIC [CAPITEC BANK LIMITED] Route 196.13.244.0/24 [AS328405] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LFSD1-AFRINIC [Link Development] but owned by ORG-LDFD1-AFRINIC [Link Datacenter For Data Circulation] Route 196.13.251.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ194-AFRINIC [South African Council of Churches] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.13.254.0/24 [AS37675] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DSL3-AFRINIC [Digicall Solutions (Pty) Ltd] but owned by ORG-SL84-AFRINIC [SkyWire (PTY) LTD] Route 196.15.152.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TSL2-AFRINIC [Telkom SA Ltd.] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.16.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.8.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.72.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63956] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.72.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS263812] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.122.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS397373] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44066] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS50867] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.16.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.76.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38001] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.114.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42831] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.168.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.216.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63956] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45382] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44066] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS45382] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.17.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.0.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.158.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42831] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.164.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.172.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS134451] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203833] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.180.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38001] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9009] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38001] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.18.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.8.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.106.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS38001] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.176.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63018] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.214.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS263812] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS62864] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS396356] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20860] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS262287] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63956] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS23679] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.19.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20860] Prefix was owned by ORG-IA41-AFRINIC [Network and Information Technology Limited] Route 196.20.0.0/19 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NIDF1-AFRINIC [Namibian Internet Development Foundation] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.20.4.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NIDF1-AFRINIC [Namibian Internet Development Foundation] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.20.9.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NIDF1-AFRINIC [Namibian Internet Development Foundation] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.20.22.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NIDF1-AFRINIC [Namibian Internet Development Foundation] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.20.30.0/24 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NIDF1-AFRINIC [Namibian Internet Development Foundation] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.21.40.0/24 [AS37501] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UotF1-AFRINIC [University of the Free State] Route 196.21.158.0/24 [AS37501] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UotF1-AFRINIC [University of the Free State] Route 196.21.159.0/24 [AS37501] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UotF1-AFRINIC [University of the Free State] Route 196.21.164.0/22 [AS8094] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-PU1-AFRINIC [North West University] Route 196.21.180.0/23 [AS37501] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UotF1-AFRINIC [University of the Free State] Route 196.21.182.0/23 [AS37501] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UotF1-AFRINIC [University of the Free State] Route 196.21.184.0/24 [AS37501] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UotF1-AFRINIC [University of the Free State] Route 196.21.233.0/24 [AS37520] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-RU1-AFRINIC [Rhodes University] Route 196.22.0.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MHCL1-AFRINIC [Metropolitan Health Corporate Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.22.32.0/20 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FM1-AFRINIC [Federal Mogul] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.23.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-DD1-AFRINIC [Dimension Data] Route 196.24.40.0/24 [AS36982] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UCT1-AFRINIC [University of Cape Town] Route 196.24.128.0/18 [AS36982] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP1-AFRINIC [TENET (The UNINET Project)] but owned by ORG-UCT1-AFRINIC [University of Cape Town] Route 196.26.86.0/24 [AS32398] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DD1-AFRINIC [Dimension Data] but owned by ORG-RII1-AFRINIC [Real Image Internet] Route 196.27.64.0/19 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.64.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.64.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.65.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.66.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.67.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.78.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.80.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.27.96.0/20 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 196.27.112.0/20 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 196.27.136.0/24 [AS37661] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-OAUI1-AFRINIC [Obafemi Awolowo University, Ife] but owned by ORG-NRaE1-AFRINIC [Nigerian Research and Education Network Limited by Guarantee] Route 196.28.5.0/24 [AS37153] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NIS1-AFRINIC [Network Information Services] but owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 196.29.56.0/21 [AS6968] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DNS1-AFRINIC [Domain Name Services] but owned by ORG-US7-AFRINIC [ZA CENTRAL REGISTRY NPC] Route 196.29.163.0/24 [AS15706] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KTL1-AFRINIC [Kanar Telecommunication (Canar Telecom Co.Ltd)] but owned by ORG-SA54-AFRINIC [Sudatel (Sudan Telecom Co. Ltd)] Route 196.32.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36666] Prefix was owned by ORG-GC6-AFRINIC [Genious Communications] Route 196.32.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36666] Prefix was owned by ORG-GC6-AFRINIC [Genious Communications] Route 196.37.91.0/24 [AS32398] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DD1-AFRINIC [Dimension Data] but owned by ORG-RII1-AFRINIC [Real Image Internet] Route 196.38.131.0/24 [AS327749] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DD1-AFRINIC [Dimension Data] but owned by ORG-DOS1-AFRINIC [Digital Outsource Services Ltd] Route 196.40.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42235] Prefix was owned by ORG-IL21-AFRINIC [IS - Internet Solutions Mozambique, Limitada] Route 196.41.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-DPBO1-AFRINIC [Vox Telecom Ltd] Route 196.41.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.36.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.50.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.54.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198381] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.60.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.62.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-RL2-AFRINIC [RAHA Ltd] Route 196.41.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2635] Prefix was owned by ORG-BML2-AFRINIC [Bubblestorm Management (Pty) Ltd] Route 196.41.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ONDP2-AFRINIC [Office National De Poste(La Poste Tunisienne)] Route 196.43.96.0/19 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.96.0/20 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.96.0/23 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.96.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.97.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.98.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.99.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.100.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.101.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.102.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.103.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.104.0/23 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.104.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.105.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.106.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.107.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.110.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.112.0/20 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.112.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.113.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.114.0/23 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.114.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.115.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.116.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.117.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.120.0/22 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 196.43.120.0/24 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 196.43.121.0/24 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 196.43.122.0/24 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 196.43.123.0/24 [AS36877] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 196.43.124.0/23 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.124.0/24 [AS37183] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AOZ1-AFRINIC [AFRICA ONLINE ZIMBABWE] but owned by ORG-UISL1-AFRINIC [Utande Internet Services (Pvt) Ltd] Route 196.43.234.0/24 [AS30619] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IIoI1-AFRINIC [INTIC (National Institute of ICT)] but owned by ORG-TMTS1-AFRINIC [TMCEL - Mo??ambique Telecom, SA] Route 196.43.249.0/24 [AS37057] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LNIC1-AFRINIC [Lesotho Network Information Centre Proprietary] but owned by ORG-VLL1-AFRINIC [Vodacom Lesotho (Pty) Ltd] Route 196.44.64.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.65.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.70.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.72.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.73.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.74.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.75.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.76.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.77.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.78.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.79.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.80.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.81.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.82.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.83.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.84.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.85.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.86.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.87.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.88.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.89.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.92.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.93.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.94.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.95.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS4637] Prefix was owned by ORG-ECO1-AFRINIC [Ecoband Ltd] Route 196.44.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209854] Prefix was owned by ORG-ECO1-AFRINIC [Ecoband Ltd] Route 196.44.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3320] Prefix was owned by ORG-ECO1-AFRINIC [Ecoband Ltd] Route 196.44.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3320] Prefix was owned by ORG-ECO1-AFRINIC [Ecoband Ltd] Route 196.44.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7018] Prefix was owned by ORG-ECO1-AFRINIC [Ecoband Ltd] Route 196.44.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3320] Prefix was owned by ORG-ECO1-AFRINIC [Ecoband Ltd] Route 196.44.160.0/20 [AS22354] in DFZ matched an AfriNIC allocation but no organisation object was found for the ASN Route 196.44.225.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.226.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.230.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.44.231.0/24 [AS37239] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BA1-AFRINIC [BCS Group (BCSNet)] but owned by ORG-IML1-AFRINIC [ICTGlobe Management (Pty) Ltd] Route 196.45.188.0/24 [AS328919] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA17-AFRINIC [NIC.MW] but owned by ORG-OCL2-AFRINIC [Open Connect Limited] Route 196.45.190.0/24 [AS36969] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NA17-AFRINIC [NIC.MW] but owned by ORG-MTL5-AFRINIC [Malawi Telecommunications Limited] Route 196.45.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-QPL1-AFRINIC [Q-Kon PTY LTD] Route 196.45.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS22351] Prefix was owned by ORG-QPL1-AFRINIC [Q-Kon PTY LTD] Route 196.46.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 196.46.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 196.46.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 196.46.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 196.46.124.0/24 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 196.46.125.0/24 [AS37146] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-RTA1-AFRINIC [Hai Telecommunications Limited] Route 196.46.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.46.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 196.46.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS59895] Prefix was owned by ORG-CNT1-AFRINIC [City Net Telecom] Route 196.46.224.0/21 [AS37179] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EBS1-AFRINIC [Ensync Business Solutions (PTY)Ltd] but owned by ORG-AINE1-AFRINIC [Africa Independent Network Exchange (Pty) LTD (AfricaINX)] Route 196.47.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS39356] Prefix was owned by ORG-AOOL1-AFRINIC [Africa Online Operations (Mauritius) Limited] Route 196.48.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.49.2.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IAoN1-AFRINIC [Internet Exchange Point Association of Namibia] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 196.49.48.0/24 [AS36864] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AMDR1-AFRINIC [Autorit?? Malienne de Regulation des T??l??commincations/TIC et Postes (AMRTP)] but owned by ORG-AMS4-AFRINIC [AFRIBONE MALI SA] Route 196.49.76.0/23 [AS37020] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-Ispa1-AFRINIC [Internet service provider association - DRC] but owned by ORG-CD1-AFRINIC [CELTEL DRC] Route 196.50.16.0/22 [AS21271] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RNDE1-AFRINIC [R??seau National d'Education et de Recherche du Mali - MALIREN] but owned by ORG-SoMT1-AFRINIC [Society of Mali's Telecommunications (SOTELMA)] Route 196.50.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCML1-AFRINIC [Gateway Communications Mozambique, Limidata] Route 196.51.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400463] Prefix was owned by ORG-ECSC1-AFRINIC [E-Com Cloud Solution Co., Ltd] Route 196.51.128.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS400463] Prefix was owned by ORG-ECSC1-AFRINIC [E-Com Cloud Solution Co., Ltd] Route 196.56.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.57.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.57.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.57.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.57.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.57.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.57.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.58.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.58.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.58.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.58.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.60.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-ZIE1-AFRINIC [Zimbabwe Internet Exchange] Route 196.61.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS204720] Prefix was owned by ORG-II1-AFRINIC [IPTP Inc] Route 196.61.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS203429] Prefix was owned by ORG-II1-AFRINIC [IPTP Inc] Route 196.61.208.0/21 [AS16637] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MBSL1-AFRINIC [MTN Business Solutions (Botswana)] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 196.168.0.0/14 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.0.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.24.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.168.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.16.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.24.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.28.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.169.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.144.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.208.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.170.240.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.192.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.171.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 196.192.16.0/24 [AS328228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UA4-AFRINIC [Universite Abomey-Calavi] but owned by ORG-SBDN1-AFRINIC [SOCIETE BENINOISE D'INFRASTRUCTURES NUMERIQUES] Route 196.192.31.0/24 [AS328702] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UA4-AFRINIC [Universite Abomey-Calavi] but owned by ORG-APLD1-AFRINIC [Agence pour le Developpement du Num??rique] Route 196.192.96.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.192.97.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.192.100.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.192.110.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.196.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.2.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205056] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.14.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.22.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.24.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS205056] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.33.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.35.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64267] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS60485] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.250.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.196.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.4.0/24 [AS328137] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FGI1-AFRINIC [Fiber Grid INC] but owned by ORG-WSCL1-AFRINIC [Web Squad Connect (Pty) Ltd] Route 196.197.6.0/24 [AS328137] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FGI1-AFRINIC [Fiber Grid INC] but owned by ORG-WSCL1-AFRINIC [Web Squad Connect (Pty) Ltd] Route 196.197.7.0/24 [AS328137] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-FGI1-AFRINIC [Fiber Grid INC] but owned by ORG-WSCL1-AFRINIC [Web Squad Connect (Pty) Ltd] Route 196.197.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.197.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.13.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.198.211.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.199.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.200.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 196.200.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 196.200.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 196.200.43.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.200.116.0/24 [AS37350] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA74-AFRINIC [IS InternetSolutions Limited] but owned by ORG-IISG1-AFRINIC [Dimension Data Ltd] Route 196.200.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 196.200.248.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 196.200.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 196.200.254.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SCS2-AFRINIC [Cimecom - Nortis] Route 196.201.1.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 196.201.10.0/24 [AS37019] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RA4-AFRINIC [RCS-Communication] but owned by ORG-IAL1-AFRINIC [INTERSAT AFRICA LTD] Route 196.201.11.0/24 [AS37019] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RA4-AFRINIC [RCS-Communication] but owned by ORG-IAL1-AFRINIC [INTERSAT AFRICA LTD] Route 196.201.16.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 196.201.20.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 196.201.128.0/19 [AS5713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ACL2-AFRINIC [Afsat Communications Ltd] but owned by ORG-TSL2-AFRINIC [Telkom SA Ltd.] Route 196.201.228.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.201.240.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 196.201.241.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 196.201.242.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 196.201.243.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 196.201.244.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 196.201.245.0/24 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EC2-AFRINIC [Egypt Centers] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 196.202.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.202.160.0/19 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.161.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.162.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48137] Prefix was owned by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] Route 196.202.164.0/24 [AS328724] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-IAKL1-AFRINIC [ISAT AFRICA KENYA LTD] Route 196.202.165.0/24 [AS328724] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-IAKL1-AFRINIC [ISAT AFRICA KENYA LTD] Route 196.202.166.0/24 [AS328724] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-IAKL1-AFRINIC [ISAT AFRICA KENYA LTD] Route 196.202.167.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.202.168.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.202.169.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.170.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.172.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.174.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.176.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.177.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.202.180.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.202.181.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.182.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.185.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.202.186.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.187.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.189.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.202.190.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 196.203.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.0.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.2.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.4.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.9.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.10.0/23 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.12.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.13.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.16.0/21 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.24.0/23 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.26.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.28.0/22 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.32.0/21 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.40.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.42.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.43.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.44.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.46.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.50.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.53.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.54.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.56.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.58.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.58.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.59.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.60.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.60.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.62.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.72.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.74.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.76.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.77.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.78.0/23 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.78.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.79.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.80.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.81.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.85.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.86.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.88.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.91.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.96.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.100.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.102.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.108.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.112.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 196.203.117.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.125.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.126.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.128.0/21 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.128.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.143.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.144.0/22 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.148.0/23 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.151.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.152.0/21 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.173.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 196.203.175.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.178.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.180.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.188.0/23 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.190.0/24 [AS37717] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CDCE1-AFRINIC [Centre de Calcul El Khawarizmi] Route 196.203.192.0/22 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.196.0/22 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 196.203.200.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.204.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.206.0/23 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.208.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.212.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.214.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.215.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.216.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.223.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.224.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 196.203.236.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.236.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS7155] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.238.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.239.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.240.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.247.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.203.248.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 196.203.251.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.252.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 196.203.254.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 196.204.160.0/21 [AS33782] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RT2-AFRINIC [Vodafone Data] but owned by ORG-BA2-AFRINIC [Bibliotheca Alexandrina] Route 196.204.168.0/21 [AS33782] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RT2-AFRINIC [Vodafone Data] but owned by ORG-BA2-AFRINIC [Bibliotheca Alexandrina] Route 196.204.176.0/21 [AS33782] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RT2-AFRINIC [Vodafone Data] but owned by ORG-BA2-AFRINIC [Bibliotheca Alexandrina] Route 196.204.184.0/21 [AS33782] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RT2-AFRINIC [Vodafone Data] but owned by ORG-BA2-AFRINIC [Bibliotheca Alexandrina] Route 196.204.208.0/24 [AS6713] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-RT2-AFRINIC [Vodafone Data] but owned by ORG-ONdP1-AFRINIC [Office National des Postes et Telecommunications ONPT (Maroc Telecom) / IAM] Route 196.207.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 196.207.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 196.207.23.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 196.207.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 196.207.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS209242] Prefix was owned by ORG-VA67-AFRINIC [Vodacom] Route 196.207.164.0/23 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 196.207.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.192.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.192.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.194.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.198.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.200.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.208.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.209.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.210.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.216.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.220.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.224.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.226.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.230.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.207.252.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 196.216.24.0/21 [AS24863] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TUOB1-AFRINIC [Technische Universitat Berlin (Campus- El Gouna)] but owned by ORG-LE1-AFRINIC [Link Egypt (Link.NET)] Route 196.216.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65200] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.80.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.216.81.0/24 [AS37006] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ASRL1-AFRINIC [Liquid Telecommunication Rwanda Limited] Route 196.216.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.90.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.92.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 196.216.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-ADBA1-AFRINIC [African Development Bank - AFDB] Route 196.216.212.0/24 [AS327820] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GDEG1-AFRINIC [GROUPEMENT D'INTERET ECONOMIQUE GROUPE COMMERCIAL BANK - GIE GCB] but owned by ORG-SP3-AFRINIC [SWECOM PLC] Route 196.216.220.0/23 [AS329109] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MOIA1-AFRINIC [Ministry of Information and Communications, Government of Sierra Leone] but owned by ORG-ZL5-AFRINIC [Zoodlabs(SL) Limited] Route 196.216.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44444] Prefix was owned by ORG-WA4-AFRINIC [Forcepoint Mauritius] Route 196.216.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS44444] Prefix was owned by ORG-WA4-AFRINIC [Forcepoint Mauritius] Route 196.218.0.0/15 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.218.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.218.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.218.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.219.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS65550] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 196.220.192.0/20 [AS37661] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NAU1-AFRINIC [Nnamdi Azikiwe University] but owned by ORG-NRaE1-AFRINIC [Nigerian Research and Education Network Limited by Guarantee] Route 196.221.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS36893] Prefix was owned by ORG-RT2-AFRINIC [Vodafone Data] Route 196.223.4.0/24 [AS29571] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CdIE1-AFRINIC [Cote d'Ivoire Internet Exchange Point] but owned by ORG-OCD2-AFRINIC [Orange C??te d'Ivoire] Route 196.223.27.0/24 [AS37440] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-MISP1-AFRINIC [Malawi Internet Service Providers Association - MISPA] but owned by ORG-ZM1-AFRINIC [Airtel Malawi Ltd] Route 196.223.48.0/21 [AS37153] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-DA9-AFRINIC [Datasync] but owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 196.223.175.0/24 [AS328354] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ML5-AFRINIC [MyISP Limited] but owned by ORG-COL2-AFRINIC [CABLE ONE LIMITED] Route 196.240.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.38.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.62.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.240.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS40676] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.241.63.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.241.64.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.241.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.241.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.241.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.11.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.242.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.243.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.243.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.10.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.244.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.7.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.9.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.174.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.232.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.237.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.238.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.239.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.245.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.245.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.1.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.4.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.5.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.16.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.17.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.18.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS63119] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.26.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.29.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.48.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.50.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.51.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.58.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.60.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS48950] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.173.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.174.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS46805] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.231.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.234.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.236.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.244.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS58065] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS57858] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.247.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS41564] Prefix was owned by ORG-FGI1-AFRINIC [Fiber Grid INC] Route 196.248.0.0/16 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.248.0.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.248.1.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.248.128.0/17 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.249.0.0/18 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.249.0.0/19 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.249.32.0/19 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UP10-AFRINIC [University of Pretoria] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.250.232.0/21 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WSA1-AFRINIC [WIOCC SOUTH AFRICA (PTY)LTD] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 196.250.232.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WSA1-AFRINIC [WIOCC SOUTH AFRICA (PTY)LTD] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 196.250.234.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WSA1-AFRINIC [WIOCC SOUTH AFRICA (PTY)LTD] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 196.250.236.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WSA1-AFRINIC [WIOCC SOUTH AFRICA (PTY)LTD] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 196.250.237.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WSA1-AFRINIC [WIOCC SOUTH AFRICA (PTY)LTD] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 196.250.238.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WSA1-AFRINIC [WIOCC SOUTH AFRICA (PTY)LTD] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 196.250.239.0/24 [AS37662] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-WSA1-AFRINIC [WIOCC SOUTH AFRICA (PTY)LTD] but owned by ORG-WIOC1-AFRINIC [West Indian Ocean Cable Company] Route 196.250.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS715] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 196.251.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS149208] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401116] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401120] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401109] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212666] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401116] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401116] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401116] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401116] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS401116] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS9304] Prefix was owned by ORG-SIL3-AFRINIC [Secure Internet Limited] Route 196.251.148.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LCAI1-AFRINIC [Leal Communication and informatics ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 196.251.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS3491] Prefix was owned by ORG-GCTL1-AFRINIC [Gateway Communications (Pty) Ltd] Route 196.251.244.0/22 [AS328608] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LCSL1-AFRINIC [Larus cloud service Limited] but owned by ORG-AOC1-AFRINIC [Africa on Cloud] Route 196.251.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 196.251.249.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS212384] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 196.251.250.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS61317] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 196.251.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS399073] Prefix was owned by ORG-DAL1-AFRINIC [Internet Utilities Africa (PTY) LTD] Route 196.251.252.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS715] Prefix was owned by ORG-WL6-AFRINIC [Woodynet Ltd] Route 196.252.228.0/23 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-PU1-AFRINIC [North West University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 196.254.0.0/15 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-UotF1-AFRINIC [University of the Free State] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 197.0.0.0/11 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.0.0.0/16 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.0.0.0/17 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.0.128.0/17 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.1.0.0/17 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.1.128.0/17 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.2.0.0/16 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.2.0.0/17 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.2.128.0/17 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.0.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.1.0/24 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.4.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.8.0/22 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.12.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.3.24.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.3.25.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.3.27.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.3.28.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.3.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.3.32.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.3.32.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.3.33.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.3.34.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.3.35.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.3.36.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.3.64.0/18 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.128.0/18 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.192.0/18 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.3.240.0/20 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.4.0.0/15 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.4.0.0/16 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.5.0.0/16 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.6.0.0/15 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.6.0.0/16 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.7.0.0/16 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.8.0.0/15 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.8.0.0/16 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.9.0.0/16 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.10.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.48.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.52.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.56.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.57.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.58.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.64.0/20 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.80.0/21 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.88.0/21 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.96.0/20 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.112.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.113.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.114.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.115.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.116.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.117.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.118.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.119.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.120.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.121.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.122.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.123.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.125.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.126.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.127.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.160.0/20 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.176.0/21 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.184.0/21 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.192.0/20 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.208.0/20 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.224.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.10.234.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.235.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.10.251.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.0.0/19 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.34.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.37.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.40.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.44.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.45.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.46.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.47.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS5438] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.11.64.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.65.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.66.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.67.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.68.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.69.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.70.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.71.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.80.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.84.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.92.0/22 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.96.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.97.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 197.11.128.0/20 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.11.144.0/21 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.11.157.0/24 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.11.160.0/19 [AS328880] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SISS1-AFRINIC [STE INTERNET SMART SOLUTIONS] Route 197.12.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS37703] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 197.12.40.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.12.64.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.12.96.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.12.108.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.12.112.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.0.0/16 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.0.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.4.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.5.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.6.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.7.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.8.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.9.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.10.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.11.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.12.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.13.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.14.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.16.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.17.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.18.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.20.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.21.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.22.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.24.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.26.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.29.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.30.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.30.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.32.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.34.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.36.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.41.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.124.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.132.0/23 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.144.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.152.0/22 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.160.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.162.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.163.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.170.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.13.171.0/24 [AS37504] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-MT2-AFRINIC [EO Data Center] Route 197.14.1.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.2.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.8.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.8.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.10.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.12.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.12.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.14.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.16.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.16.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.24.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.32.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.32.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.40.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.48.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.48.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.50.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.52.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.52.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.54.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.14.56.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.15.0.0/18 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.15.64.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.15.96.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.15.128.0/18 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.15.192.0/18 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.16.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.16.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.16.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.0.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.0.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.2.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.4.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.4.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.6.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.8.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.8.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.10.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.12.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.12.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.14.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.16.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.16.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.18.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.20.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.20.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.22.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.24.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.24.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.26.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.28.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.28.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.30.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.32.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.32.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.34.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.64.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.64.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.66.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.68.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.68.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.70.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.72.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.72.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.76.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.80.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.80.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.88.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.96.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.96.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.104.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.112.0/20 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.112.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.120.0/21 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.128.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.128.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.130.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.132.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.132.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.134.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.136.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.136.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.138.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.140.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.140.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.142.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.144.0/22 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.144.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.17.146.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.18.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.18.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.18.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.19.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.19.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.19.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.20.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.20.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.20.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.21.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.21.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.21.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.22.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.22.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.22.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.23.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.23.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.23.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.24.0.0/16 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.24.0.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.24.128.0/17 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 197.25.0.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.25.0.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.25.0.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.25.32.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.25.64.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.25.64.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.25.96.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.25.128.0/17 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.26.0.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.26.0.0/20 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.26.10.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.26.16.0/20 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.26.32.0/19 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.26.64.0/18 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 197.26.128.0/18 [AS37705] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TA40-AFRINIC [TOPNET] Route 197.26.192.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.26.192.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.26.224.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.0.0/16 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.0.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.0.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.0.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.64.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.128.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.128.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.27.192.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.28.0.0/15 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.28.0.0/16 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.28.0.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.28.128.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.29.0.0/16 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.29.0.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.29.120.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.29.122.0/24 [AS37447] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CCTs2-AFRINIC [ORANGE RDC] Route 197.29.123.0/24 [AS37461] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OG1-AFRINIC [ORANGE GUINEE] Route 197.29.125.0/24 [AS37447] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-CCTs2-AFRINIC [ORANGE RDC] Route 197.29.126.0/24 [AS328126] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.29.128.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.30.0.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.30.0.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.30.64.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.30.128.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.32.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.32.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.48.0/21 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.48.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.52.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.56.0/21 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.56.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.60.0/22 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.64.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.64.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.96.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.128.0/17 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.128.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.128.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.160.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.192.0/18 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.192.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.31.224.0/19 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 197.32.0.0/11 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.32.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.35.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.36.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.37.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.37.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.37.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.37.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.38.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.39.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.32.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.36.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.40.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.56.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.60.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.64.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.68.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.96.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.104.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.112.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.116.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.128.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.144.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.148.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.152.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.156.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.176.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.42.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.43.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.44.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.45.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.45.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.45.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.45.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.46.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.47.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.47.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.47.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.47.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.48.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.48.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.48.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.48.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.49.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.51.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.51.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.51.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.51.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.52.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.53.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.53.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.53.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.53.192.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.54.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.55.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.56.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.57.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.58.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.59.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.60.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.0.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.63.224.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 197.79.0.0/17 [AS37611] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VSA1-AFRINIC [MTN SA] but owned by ORG-AS7-AFRINIC [AFRIHOST SP (PTY) LTD] Route 197.103.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6220] Prefix was owned by ORG-DD1-AFRINIC [Dimension Data] Route 197.148.88.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198381] Prefix was owned by ORG-IA46-AFRINIC [ITELNET] Route 197.148.92.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198394] Prefix was owned by ORG-IA46-AFRINIC [ITELNET] Route 197.148.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.100.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.104.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.108.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.120.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24691] Prefix was owned by ORG-TT1-AFRINIC [Togo Telecom] Route 197.148.140.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AM2-AFRINIC [Airtel Madagascar] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 197.149.144.0/22 [AS37667] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IB1-AFRINIC [I-Net Bridge] but owned by ORG-ISAL1-AFRINIC [IRESS South Africa (AUSTRALIA) (PTY) LTD] Route 197.149.180.0/22 [AS37356] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JTL2-AFRINIC [JIREH Technologies (PTY) Ltd.] but owned by ORG-SI5-AFRINIC [Huge Networks (Pty) Ltd] Route 197.149.180.0/24 [AS37356] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JTL2-AFRINIC [JIREH Technologies (PTY) Ltd.] but owned by ORG-SI5-AFRINIC [Huge Networks (Pty) Ltd] Route 197.149.181.0/24 [AS37356] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JTL2-AFRINIC [JIREH Technologies (PTY) Ltd.] but owned by ORG-SI5-AFRINIC [Huge Networks (Pty) Ltd] Route 197.149.182.0/24 [AS37356] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JTL2-AFRINIC [JIREH Technologies (PTY) Ltd.] but owned by ORG-SI5-AFRINIC [Huge Networks (Pty) Ltd] Route 197.149.183.0/24 [AS37356] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-JTL2-AFRINIC [JIREH Technologies (PTY) Ltd.] but owned by ORG-SI5-AFRINIC [Huge Networks (Pty) Ltd] Route 197.155.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 197.155.83.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 197.155.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 197.155.224.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 197.155.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 197.157.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-IA46-AFRINIC [ITELNET] Route 197.157.219.0/24 [AS329267] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-KTL2-AFRINIC [KKON Technologies Ltd] but owned by ORG-FBL5-AFRINIC [FIBERONE BROADBAND LTD] Route 197.157.240.0/23 [AS327923] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-EPL2-AFRINIC [IOCO Infrastructure Services (Pty) Ltd] but owned by ORG-SABS1-AFRINIC [South African Bankers Services Company Limited] Route 197.158.92.0/24 [AS37037] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GM1-AFRINIC [Gulfsat Madagascar] but owned by ORG-OM2-AFRINIC [Orange Madagascar] Route 197.159.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64981] Prefix was owned by ORG-CSdT1-AFRINIC [Companhia Santomense de Telecomunicacoes] Route 197.159.176.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64981] Prefix was owned by ORG-CSdT1-AFRINIC [Companhia Santomense de Telecomunicacoes] Route 197.210.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.2.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.3.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.6.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.10.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.12.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.19.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.20.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.21.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.30.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.31.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.32.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.49.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.52.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.53.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.55.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.96.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.97.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.98.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.99.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.102.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.103.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.104.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.105.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.106.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.107.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.108.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.109.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.110.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.111.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.112.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.113.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.114.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.116.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.117.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.118.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.119.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.123.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.124.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.126.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.127.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.128.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.129.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.130.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.131.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.132.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.133.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.134.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.135.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.136.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.137.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.138.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.139.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.140.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.141.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.142.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.143.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.144.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.145.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.146.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.147.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.148.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.149.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.150.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.151.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.152.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.153.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.154.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.155.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.156.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.157.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.158.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.159.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.160.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.161.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.163.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.164.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.165.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.166.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.167.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.168.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.169.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.170.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.177.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.178.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.179.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.180.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.181.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.182.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.183.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.184.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.185.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.186.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.187.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.188.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.189.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.192.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.193.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.194.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.195.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.196.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.197.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.198.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.199.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.200.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.201.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.202.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.203.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.204.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.205.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.206.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.207.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.208.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.212.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.213.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.214.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.215.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.216.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.217.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.218.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.219.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.220.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.221.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.223.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.224.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.225.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.226.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.227.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.228.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.229.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.230.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.232.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.233.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.234.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.235.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.246.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.247.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.248.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.252.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.253.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.254.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.210.255.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29465] Prefix was owned by ORG-MN1-AFRINIC [MTN Nigeria] Route 197.211.0.0/19 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.0.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.211.1.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.2.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.3.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.5.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.6.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.7.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.8.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.211.9.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.11.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.13.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.14.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.15.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198394] Prefix was owned by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] Route 197.211.20.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.22.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.211.24.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.25.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.26.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.27.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.28.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.29.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.31.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.211.128.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS51265] Prefix was owned by ORG-BA1-AFRINIC [BCS Group (BCSNet)] Route 197.211.192.0/19 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.213.0/24 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.216.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.218.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.220.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.222.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.224.0/19 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.228.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.230.0/23 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.244.0/22 [AS37332] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] but owned by ORG-ZO1-AFRINIC [Zimbabwe Online] Route 197.211.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS64631] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 197.214.56.0/24 [AS327708] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AN2-AFRINIC [Airtel Niger] but owned by ORG-ARL2-AFRINIC [Airtel Rwanda Ltd] Route 197.214.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-OB4-AFRINIC [Orange Bissau] Route 197.214.100.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-HL1-AFRINIC [Hyperia Limited] Route 197.214.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-HL1-AFRINIC [Hyperia Limited] Route 197.215.222.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS43256] Prefix was owned by ORG-GBS1-AFRINIC [Global Broadband Solution] Route 197.220.84.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.88.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.89.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.90.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.91.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.92.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.93.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.94.0/24 [AS37371] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GIC1-AFRINIC [Global Internet Company] but owned by ORG-HTSI1-AFRINIC [Hormuud Telecom Somalia INC] Route 197.220.96.0/19 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.96.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.98.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.99.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.100.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.101.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.220.102.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.104.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.220.105.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.220.106.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.220.107.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.220.108.0/22 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.108.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.109.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.112.0/21 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.113.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.114.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.115.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.118.0/23 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.118.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.119.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.220.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198381] Prefix was owned by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] Route 197.220.122.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS198394] Prefix was owned by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] Route 197.220.123.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.124.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.126.0/24 [AS15399] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-WOL1-AFRINIC [Wananchi Group (Kenya) Limited] Route 197.220.127.0/24 [AS37027] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SCL5-AFRINIC [Simbanet Com (K) Ltd] but owned by ORG-SL71-AFRINIC [Simbanet (T) Limited] Route 197.220.128.0/19 [AS33567] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NUoL1-AFRINIC [National University of Lesotho] but owned by ORG-TLL1-AFRINIC [Econet Telecom Lesotho (PTY) LTD] Route 197.224.0.0/14 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.0.0/16 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.0.0/17 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.0.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.0.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.0.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.2.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.3.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.40.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.41.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.60.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.64.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.66.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.67.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.80.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.104.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.112.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.128.0/17 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.132.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.136.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.144.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.160.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.200.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.232.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.253.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.254.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.224.254.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.0.0/16 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.0.0/17 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.0.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.0.0/19 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.16.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.32.0/19 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.64.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.64.0/19 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.96.0/19 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.128.0/17 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.128.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.144.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.146.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.160.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.161.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.162.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.165.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.166.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.167.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.168.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.170.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.171.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.172.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.173.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.225.192.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.0.0/16 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.0.0/17 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.0.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.0.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.24.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.64.0/18 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.128.0/17 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.134.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.134.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.135.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.136.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.144.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.160.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.176.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.192.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.224.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.226.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.227.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.229.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.230.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.241.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.226.254.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.0.0/16 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.1.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.2.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.4.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.4.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.5.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.6.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.8.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.11.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.12.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.15.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.17.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.18.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.23.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.28.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.29.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.32.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.34.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.35.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.37.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.40.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.41.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.42.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.46.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.48.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.48.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.48.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.48.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.49.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.50.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.51.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.52.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.52.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.53.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.54.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.55.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.56.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.56.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.56.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.56.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.57.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.58.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.58.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.59.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.60.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.60.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.64.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.90.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.112.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.128.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.136.0/21 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.144.0/22 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.150.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.176.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.227.192.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 197.231.152.0/21 [AS37410] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CLI2-AFRINIC [NOVAFONE Inc] but owned by ORG-LCC1-AFRINIC [Lonestar Communications Corporation] Route 197.231.155.0/24 [AS37410] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CLI2-AFRINIC [NOVAFONE Inc] but owned by ORG-LCC1-AFRINIC [Lonestar Communications Corporation] Route 197.231.156.0/24 [AS37410] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CLI2-AFRINIC [NOVAFONE Inc] but owned by ORG-LCC1-AFRINIC [Lonestar Communications Corporation] Route 197.231.220.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS39287] Prefix was owned by ORG-CS10-AFRINIC [Cyberdyne S.A.] Route 197.234.41.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SBaC1-AFRINIC [Steam Broadcasting and Communications Limited] Route 197.234.42.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SBaC1-AFRINIC [Steam Broadcasting and Communications Limited] Route 197.234.43.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SBaC1-AFRINIC [Steam Broadcasting and Communications Limited] Route 197.234.54.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SBaC1-AFRINIC [Steam Broadcasting and Communications Limited] Route 197.234.59.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SBaC1-AFRINIC [Steam Broadcasting and Communications Limited] Route 197.234.61.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS29286] Prefix was owned by ORG-SBaC1-AFRINIC [Steam Broadcasting and Communications Limited] Route 197.234.240.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CAL2-AFRINIC [CloudFlare Africa Ltd] Route 197.234.241.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CAL2-AFRINIC [CloudFlare Africa Ltd] Route 197.234.242.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CAL2-AFRINIC [CloudFlare Africa Ltd] Route 197.234.243.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS13335] Prefix was owned by ORG-CAL2-AFRINIC [CloudFlare Africa Ltd] Route 197.242.32.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6453] Prefix was owned by ORG-TCU1-AFRINIC [TATA Communications] Route 197.242.48.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS6453] Prefix was owned by ORG-TCU1-AFRINIC [TATA Communications] Route 197.242.49.0/24 [AS33763] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-TCU1-AFRINIC [TATA Communications] but owned by ORG-PTL5-AFRINIC [Paratus Telecommunications Limited] Route 197.242.84.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS24940] Prefix was owned by ORG-HC1-AFRINIC [Xneelo (Pty) Ltd] Route 197.242.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS42235] Prefix was owned by ORG-IL21-AFRINIC [IS - Internet Solutions Mozambique, Limitada] Route 197.243.0.0/17 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.0.0/18 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.0.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.0.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.4.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.8.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.12.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.16.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.32.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.32.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.36.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.39.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.42.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.43.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.44.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.47.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.48.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.48.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.52.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.56.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.60.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.64.0/18 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.64.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.64.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.67.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.68.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.72.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.76.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.80.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.80.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.84.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.88.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.92.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.96.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.96.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.100.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.104.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.108.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.112.0/20 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.112.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.115.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.116.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.118.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.119.0/24 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.120.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.243.124.0/22 [AS37228] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-BSC1-AFRINIC [Broadband Systems Corporation] but owned by ORG-ORN1-AFRINIC [KT RWANDA NETWORK Ltd] Route 197.249.0.0/16 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.0.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.4.0/22 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.8.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.96.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.96.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.128.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.192.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.224.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.232.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.240.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.249.248.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS25139] Prefix was owned by ORG-TM1-AFRINIC [TVCABO Mocambique] Route 197.254.0.0/17 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.0.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.0.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.16.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.32.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.39.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.48.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.64.0/18 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.64.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.80.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.254.101.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS15808] Prefix was owned by ORG-CSL1-AFRINIC [AccessKenya Group Ltd] Route 197.255.176.0/20 [AS36924] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GC7-AFRINIC [GVA Congo] but owned by ORG-GCDS1-AFRINIC [GVA Cote d'Ivoire SAS] Route 198.54.1.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 198.54.2.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 198.54.3.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 198.54.8.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 198.54.9.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 198.54.10.0/24 [AS37130] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ10-AFRINIC [Co-Operative Networking Services] but owned by ORG-SPL1-AFRINIC [State Information Technology Agency SOC Ltd] Route 198.54.24.0/21 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ170-AFRINIC [OSI Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.40.0/23 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ170-AFRINIC [OSI Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.42.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ170-AFRINIC [OSI Holdings Limited] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.58.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ206-AFRINIC [Central University of Technology] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.64.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ82-AFRINIC [Agricultural Research Council] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.65.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ3-AFRINIC [Technikon Witwatersrand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.66.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ3-AFRINIC [Technikon Witwatersrand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.68.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.71.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ2-AFRINIC [Hi Performance Systems (ZA)] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.80.0/24 [AS327701] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ14-AFRINIC [Sabinet Online Ltd] but owned by ORG-SG3-AFRINIC [Sabinet Gateway] Route 198.54.83.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ214-AFRINIC [University of Kwazulu-Natal] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.84.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ127-AFRINIC [The Hollard Insurance Company] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.91.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ3-AFRINIC [Technikon Witwatersrand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.149.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AA78-AFRINIC [Anglo American South Africa (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.154.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ108-AFRINIC [Digital Networking] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.155.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.163.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ188-AFRINIC [Rainbow Chickens (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.165.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ188-AFRINIC [Rainbow Chickens (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.170.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ188-AFRINIC [Rainbow Chickens (Pty) Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.173.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ3-AFRINIC [Technikon Witwatersrand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.174.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ3-AFRINIC [Technikon Witwatersrand] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.196.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ175-AFRINIC [Price Forbes] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.219.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ110-AFRINIC [Edenvale Town Council] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.223.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ173-AFRINIC [Peninsula Technikon] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.228.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ158-AFRINIC [National Brands Ltd] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 198.54.234.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ224-AFRINIC [University of the Western Cape] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.249.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.250.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.251.0/24 [AS2018] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ5-AFRINIC [Nelson Mandela Metropolitan University] but owned by ORG-UP1-AFRINIC [TENET (The UNINET Project)] Route 198.54.253.0/24 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ZZ174-AFRINIC [Persetel] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 202.123.0.0/19 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.0.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.1.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.2.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.3.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.16.0/20 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.19.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.24.0/23 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.24.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.25.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.26.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.28.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.29.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 202.123.31.0/24 [AS23889] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-SA56-AFRINIC [Telecom Plus Ltd] but owned by ORG-mA21-AFRINIC [Mauritius Telecom Ltd] Route 204.235.32.0/21 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IPL3-AFRINIC [IMPALA PLATS LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 204.235.40.0/22 [AS3741] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-IPL3-AFRINIC [IMPALA PLATS LTD] but owned by ORG-DD1-AFRINIC [Dimension Data] Route 212.96.18.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.21.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.22.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.23.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.24.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.25.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.26.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.27.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.29.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.96.31.0/24 [AS36994] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-VBAG1-AFRINIC [Vodacom Business Africa Group (PTY) Ltd] but owned by ORG-VA67-AFRINIC [Vodacom] Route 212.100.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.65.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.66.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.68.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.69.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.71.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.72.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.73.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.79.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.81.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.82.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.84.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.86.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.88.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.89.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.90.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.91.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.92.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.93.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.94.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.100.95.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS20598] Prefix was owned by ORG-CL3-AFRINIC [Cyberspace Limited] Route 212.103.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 212.103.171.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 212.103.172.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 213.150.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS2609] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 213.150.160.0/23 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 213.150.160.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 213.150.161.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 213.150.162.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS37703] Prefix was owned by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] Route 213.150.164.0/24 [AS37693] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-TS4-AFRINIC [OOREDOO TUNISIE SA] Route 213.150.170.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 213.150.172.0/23 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 213.150.174.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 213.150.175.0/24 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 213.150.180.0/23 [AS37671] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-IA51-AFRINIC [3S INF] Route 213.150.185.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 213.150.186.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 213.150.187.0/24 [AS327934] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-SNDT3-AFRINIC [SOCIETE NATIONALE DES TELECOMMUNICATIONS (Tunisie Telecom)] Route 213.150.188.0/24 [AS37492] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-ATIA2-AFRINIC [ATI - Agence Tunisienne Internet] but owned by ORG-OT3-AFRINIC [Orange Tunisie] Route 213.152.64.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.152.68.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.152.76.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.152.78.0/24 [AS37112] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-DA7-AFRINIC [Dar Al-Handasah] Route 213.152.83.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.152.85.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.152.95.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.154.32.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.154.39.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.154.40.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 213.154.64.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.64.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.64.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.67.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.68.0/23 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.70.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.72.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.74.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.75.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.76.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.77.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.78.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.80.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.80.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.85.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.87.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.154.88.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8346] Prefix was owned by ORG-SNDT1-AFRINIC [SONATEL Societe Nationale Des Telecommunications Du Senegal] Route 213.158.160.0/19 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 213.158.160.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 213.158.175.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 213.158.190.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 213.158.191.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS8452] Prefix was owned by ORG-TD2-AFRINIC [TE Data] Route 213.179.160.0/19 [AS16214] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-AARN1-AFRINIC [Algerian Academic Research Network] but owned by ORG-CA3-AFRINIC [C.E.R.I.S.T.] Route 217.14.84.0/24 [AS37672] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-GTN1-AFRINIC [Inq. Digital Nigeria] but owned by ORG-VBC1-AFRINIC [INQ DIGITAL CAMEROON SA] Route 217.21.112.0/20 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 217.21.112.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 217.21.115.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 217.21.120.0/21 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 217.21.120.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 217.21.121.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 217.21.125.0/24 in DFZ matched an AfriNIC allocation but was sourced from a non-AfriNIC ASN [AS30844] Prefix was owned by ORG-LTOL1-AFRINIC [Liquid Telecommunications Operations Limited] Route 217.52.0.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.8.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.14.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.15.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.16.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.18.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.19.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.22.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.24.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.28.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.28.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.29.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.31.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.32.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.32.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.39.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.46.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.50.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.52.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.70.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.72.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.73.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.78.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.80.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.88.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.98.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.99.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.100.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.102.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.111.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.124.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.139.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.151.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.160.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.184.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.202.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.206.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.207.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.217.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.224.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.240.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.244.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.247.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.248.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.250.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.250.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.254.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.52.255.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.0.0/17 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.16.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.64.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.72.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.80.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.87.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.88.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.96.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.104.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.110.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.113.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.114.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.117.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.118.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.125.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.126.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.128.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.144.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.152.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.160.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.179.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.180.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.184.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.192.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.200.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.208.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.210.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.211.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.214.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.216.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.217.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.224.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.232.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.236.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.240.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.244.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.246.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.248.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.249.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.250.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.251.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.53.255.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.8.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.9.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.10.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.17.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.24.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.32.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.40.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.56.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.62.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.70.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.72.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.80.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.88.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.97.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.100.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.103.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.104.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.116.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.125.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.126.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.127.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.128.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.136.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.147.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.150.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.162.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.172.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.176.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.184.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.192.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.218.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.234.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.250.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.252.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.253.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.54.255.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.0.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.0.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.16.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.32.0/19 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.32.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.48.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.72.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.80.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.81.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.82.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.83.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.84.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.85.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.88.0/24 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.128.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.128.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.132.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.136.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.144.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.144.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.152.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.160.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.168.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.176.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.176.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.184.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.192.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.192.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.196.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.200.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.208.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.208.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.216.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.224.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.232.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.234.0/23 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.236.0/22 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.240.0/20 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.240.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.55.248.0/21 [AS36992] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NO1-AFRINIC [Nile Online] but owned by ORG-EM1-AFRINIC [ETISALAT MISR] Route 217.170.156.0/22 [AS30985] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-CI11-AFRINIC [CEFIB Internet] but owned by ORG-IS28-AFRINIC [Orange Mali SA] Route 217.199.144.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.144.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.145.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.146.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.148.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.149.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.151.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.152.0/21 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] Route 217.199.153.0/24 [AS9129] in DFZ matched an AfriNIC allocation but was announced by a different AfriNIC organisation Announced by ORG-NOIS1-AFRINIC [MTN Business Kenya] but owned by ORG-VSA1-AFRINIC [MTN SA] From fhfrediani at gmail.com Fri Oct 24 13:10:27 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Fri, 24 Oct 2025 10:10:27 -0300 Subject: [rpd] AfriNIC audit data In-Reply-To: References: Message-ID: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> Yes there are legitimate cases, but when this happens it may be a signal of alert. The point is to find two things: 1) If the ASN announcing it doesn't have any relation to the resource holder and 2) If resources are being used out of the region (the worst). For the case of parent/sub-company ideally resources should be transferred among companies using them in reality then. Fernando On 10/24/2025 7:45 AM, Andrew Alston wrote: > Hi All, > > While I haven't got around to publishing the code behind this - mainly > because it by necessity exposes certain data and requires a BGP dump > from a juniper router which is hundreds of megs big, I've attached the > output of the code I wrote. > > One caveat with this data - There is nothing inherently wrong with > space allocated to an organisation being announced by a non-AfriNIC > ASN, there are many legitimate cases and reasons behind this.? The > same thing happens when space is allocated to one organisation but > announced by another, and this can happen when a sub-company of a > parent company is announcing space from their own ASN when the space > was originally allocated to the parent.? As such, when reading this > data, it's important to understand that the abnormalities?detected do > not necessarily indicate anything nefarious - and this data should not > be seen as accusations of malfeasance?against anyone. > > Let's see if the lists let this post through! > > Thanks > > Andrew > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd From aa at alstonnetworks.net Fri Oct 24 13:18:34 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Fri, 24 Oct 2025 16:18:34 +0300 Subject: [rpd] AfriNIC audit data In-Reply-To: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> References: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> Message-ID: Some companies prefer to hold all the space in the parent company and allocate it downwards themselves to sub-entities because of the way the AfriNIC fee structure works - it gets to a point where it is *far* cheaper to hold all the space in a single entity than to have seperate space held by loads of entities. With regards to space being used out of region - that's extremely difficult to actually know - because the BGP table has no knowledge of geography :) Thanks Andrew On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani wrote: > Yes there are legitimate cases, but when this happens it may be a signal > of alert. The point is to find two things: 1) If the ASN announcing it > doesn't have any relation to the resource holder and 2) If resources are > being used out of the region (the worst). > For the case of parent/sub-company ideally resources should be > transferred among companies using them in reality then. > > Fernando > > On 10/24/2025 7:45 AM, Andrew Alston wrote: > > Hi All, > > > > While I haven't got around to publishing the code behind this - mainly > > because it by necessity exposes certain data and requires a BGP dump > > from a juniper router which is hundreds of megs big, I've attached the > > output of the code I wrote. > > > > One caveat with this data - There is nothing inherently wrong with > > space allocated to an organisation being announced by a non-AfriNIC > > ASN, there are many legitimate cases and reasons behind this. The > > same thing happens when space is allocated to one organisation but > > announced by another, and this can happen when a sub-company of a > > parent company is announcing space from their own ASN when the space > > was originally allocated to the parent. As such, when reading this > > data, it's important to understand that the abnormalities detected do > > not necessarily indicate anything nefarious - and this data should not > > be seen as accusations of malfeasance against anyone. > > > > Let's see if the lists let this post through! > > > > Thanks > > > > Andrew > > > > > > _______________________________________________ > > RPD mailing list > > RPD at afrinic.net > > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From john at sanren.ac.za Fri Oct 24 13:35:51 2025 From: john at sanren.ac.za (John Hay) Date: Fri, 24 Oct 2025 15:35:51 +0200 Subject: [rpd] AfriNIC audit data In-Reply-To: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> References: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> Message-ID: There is also the case where universities and research organisations have their own address space, but it is announced from the NREN's ASN. Regards John On Fri, 24 Oct 2025 at 15:20, Fernando Frediani wrote: > Yes there are legitimate cases, but when this happens it may be a signal > of alert. The point is to find two things: 1) If the ASN announcing it > doesn't have any relation to the resource holder and 2) If resources are > being used out of the region (the worst). > For the case of parent/sub-company ideally resources should be > transferred among companies using them in reality then. > > Fernando > > On 10/24/2025 7:45 AM, Andrew Alston wrote: > > Hi All, > > > > While I haven't got around to publishing the code behind this - mainly > > because it by necessity exposes certain data and requires a BGP dump > > from a juniper router which is hundreds of megs big, I've attached the > > output of the code I wrote. > > > > One caveat with this data - There is nothing inherently wrong with > > space allocated to an organisation being announced by a non-AfriNIC > > ASN, there are many legitimate cases and reasons behind this. The > > same thing happens when space is allocated to one organisation but > > announced by another, and this can happen when a sub-company of a > > parent company is announcing space from their own ASN when the space > > was originally allocated to the parent. As such, when reading this > > data, it's important to understand that the abnormalities detected do > > not necessarily indicate anything nefarious - and this data should not > > be seen as accusations of malfeasance against anyone. > > > > Let's see if the lists let this post through! > > > > Thanks > > > > Andrew > > > > > > _______________________________________________ > > RPD mailing list > > RPD at afrinic.net > > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fhfrediani at gmail.com Fri Oct 24 13:39:04 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Fri, 24 Oct 2025 10:39:04 -0300 Subject: [rpd] AfriNIC audit data In-Reply-To: References: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> Message-ID: On Fri, 24 Oct 2025, 10:18 Andrew Alston, wrote: > > With regards to space being used out of region - that's extremely > difficult to actually know - because the BGP table has no knowledge of > geography :) > I wouldn't say it is trivial but with geolocation data plus some traveroutes and latency check it is not extremelly dificult to find out. With some intended work that can be found out and further investigate to give AfriNic all necessary information. Fernanso > > On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani > wrote: > >> Yes there are legitimate cases, but when this happens it may be a signal >> of alert. The point is to find two things: 1) If the ASN announcing it >> doesn't have any relation to the resource holder and 2) If resources are >> being used out of the region (the worst). >> For the case of parent/sub-company ideally resources should be >> transferred among companies using them in reality then. >> >> Fernando >> >> On 10/24/2025 7:45 AM, Andrew Alston wrote: >> > Hi All, >> > >> > While I haven't got around to publishing the code behind this - mainly >> > because it by necessity exposes certain data and requires a BGP dump >> > from a juniper router which is hundreds of megs big, I've attached the >> > output of the code I wrote. >> > >> > One caveat with this data - There is nothing inherently wrong with >> > space allocated to an organisation being announced by a non-AfriNIC >> > ASN, there are many legitimate cases and reasons behind this. The >> > same thing happens when space is allocated to one organisation but >> > announced by another, and this can happen when a sub-company of a >> > parent company is announcing space from their own ASN when the space >> > was originally allocated to the parent. As such, when reading this >> > data, it's important to understand that the abnormalities detected do >> > not necessarily indicate anything nefarious - and this data should not >> > be seen as accusations of malfeasance against anyone. >> > >> > Let's see if the lists let this post through! >> > >> > Thanks >> > >> > Andrew >> > >> > >> > _______________________________________________ >> > RPD mailing list >> > RPD at afrinic.net >> > https://lists.afrinic.net/mailman/listinfo/rpd >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Fri Oct 24 14:02:41 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Fri, 24 Oct 2025 17:02:41 +0300 Subject: [rpd] AfriNIC audit data In-Reply-To: References: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> Message-ID: You also have to remember, that space allocated prior to soft-landing has no geographic restrictions on where it can be used - geographic restrictions only applied to space allocated under soft landing. Secondly - geo-location is horrifically inaccurate - I can point to numerous blocks which claim they are in Mauritius but 100% aren't. I can point to blocks where geo-location claims they are in Las Vegas - when they are 100% used in Africa - the fact is most geo-location providers seem to be either using the whois data or using other metrics and are incredibly often very very far from accurate. Sadly, most of the geo-location providers refuse to implement anything resembling RFC8805 either, which would at least allow providers to publish accurate data. Thirdly - traceroutes are meaningless in terms of geo-location - for one thing - you have people using non-LEO based satellite connectivity - more than you would imagine, the latency there will tell you absolutely nothing. For another thing, when you add MPLS ttl-no-decrement to networks, which hides hops , you have no way to know where the space is being routed via - and hence latency measurements are totally out of whack. I point out that it was just yesterday when I saw the latency of a particular prefix go from 120ms odd to well over 200, purely because the provider receiving the prefix screwed up the return path - a return path which was of course invisible on the traceroute. The space was still used on continent - but the traceroute latencies told a vastly misleading story. So no - determining geographic location of space is not as simple as you make it out to be, in fact, its a massive headache that I've had to spend copious amounts of time dealing with over the years because of faulty geo-location data and geo-location ring fencing on services - so IP's showing up in the wrong location and as a result being unable to access certain things. Andrew On Fri, Oct 24, 2025 at 4:39?PM Fernando Frediani wrote: > > On Fri, 24 Oct 2025, 10:18 Andrew Alston, wrote: > >> >> With regards to space being used out of region - that's extremely >> difficult to actually know - because the BGP table has no knowledge of >> geography :) >> > > I wouldn't say it is trivial but with geolocation data plus some > traveroutes and latency check it is not extremelly dificult to find out. > > With some intended work that can be found out and further investigate to > give AfriNic all necessary information. > > Fernanso > >> >> On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani >> wrote: >> >>> Yes there are legitimate cases, but when this happens it may be a signal >>> of alert. The point is to find two things: 1) If the ASN announcing it >>> doesn't have any relation to the resource holder and 2) If resources are >>> being used out of the region (the worst). >>> For the case of parent/sub-company ideally resources should be >>> transferred among companies using them in reality then. >>> >>> Fernando >>> >>> On 10/24/2025 7:45 AM, Andrew Alston wrote: >>> > Hi All, >>> > >>> > While I haven't got around to publishing the code behind this - mainly >>> > because it by necessity exposes certain data and requires a BGP dump >>> > from a juniper router which is hundreds of megs big, I've attached the >>> > output of the code I wrote. >>> > >>> > One caveat with this data - There is nothing inherently wrong with >>> > space allocated to an organisation being announced by a non-AfriNIC >>> > ASN, there are many legitimate cases and reasons behind this. The >>> > same thing happens when space is allocated to one organisation but >>> > announced by another, and this can happen when a sub-company of a >>> > parent company is announcing space from their own ASN when the space >>> > was originally allocated to the parent. As such, when reading this >>> > data, it's important to understand that the abnormalities detected do >>> > not necessarily indicate anything nefarious - and this data should not >>> > be seen as accusations of malfeasance against anyone. >>> > >>> > Let's see if the lists let this post through! >>> > >>> > Thanks >>> > >>> > Andrew >>> > >>> > >>> > _______________________________________________ >>> > RPD mailing list >>> > RPD at afrinic.net >>> > https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From fhfrediani at gmail.com Fri Oct 24 15:05:56 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Fri, 24 Oct 2025 12:05:56 -0300 Subject: [rpd] AfriNIC audit data In-Reply-To: References: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> Message-ID: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> On 10/24/2025 11:02 AM, Andrew Alston wrote: > You also have to remember, that space allocated prior to soft-landing > has no geographic restrictions on where it can be used - geographic > restrictions only applied to space allocated under soft landing. Don't remember of this being like that. Resources registered in AfriNic region, regardless of when they were assigned are to be used majority within the region for Africa Internet development and AfriNic staff already made that clear in the past. There would be no sense to get resources from AfriNic and be able to freely use outside the region. > > > > On Fri, Oct 24, 2025 at 4:39?PM Fernando Frediani > wrote: > > > On Fri, 24 Oct 2025, 10:18 Andrew Alston, > wrote: > > > With regards to space being used out of region - that's > extremely difficult to actually know - because the BGP table > has no knowledge of geography :) > > > I wouldn't say it is trivial but with geolocation data plus some > traveroutes and latency check it is not extremelly dificult to > find out. > > With some intended work that can be found out and further > investigate to give AfriNic all necessary information. > > Fernanso > > > On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani > wrote: > > Yes there are legitimate cases, but when this happens it > may be a signal > of alert. The point is to find two things: 1) If the ASN > announcing it > doesn't have any relation to the resource holder and 2) If > resources are > being used out of the region (the worst). > For the case of parent/sub-company ideally resources > should be > transferred among companies using them in reality then. > > Fernando > > On 10/24/2025 7:45 AM, Andrew Alston wrote: > > Hi All, > > > > While I haven't got around to publishing the code behind > this - mainly > > because it by necessity exposes certain data and > requires a BGP dump > > from a juniper router which is hundreds of megs big, > I've attached the > > output of the code I wrote. > > > > One caveat with this data - There is nothing inherently > wrong with > > space allocated to an organisation being announced by a > non-AfriNIC > > ASN, there are many legitimate cases and reasons behind > this.? The > > same thing happens when space is allocated to one > organisation but > > announced by another, and this can happen when a > sub-company of a > > parent company is announcing space from their own ASN > when the space > > was originally allocated to the parent.? As such, when > reading this > > data, it's important to understand that the > abnormalities?detected do > > not necessarily indicate anything nefarious - and this > data should not > > be seen as accusations of malfeasance?against anyone. > > > > Let's see if the lists let this post through! > > > > Thanks > > > > Andrew > > > > > > _______________________________________________ > > RPD mailing list > > RPD at afrinic.net > > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Fri Oct 24 15:07:34 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Fri, 24 Oct 2025 18:07:34 +0300 Subject: [rpd] [members-discuss] AfriNIC audit data In-Reply-To: <3FDFEEE0-F7E0-4C29-B88C-C7C30E92827E@ctnmw.net> References: <3FDFEEE0-F7E0-4C29-B88C-C7C30E92827E@ctnmw.net> Message-ID: If they can run the data through and we don't have to pay for it - sure! I'm busy writing some additional code to get more data (and potentially integrate with other RIR's datasets) but before I attempt integration with other data sets I need to do some serious code optimisation, because the AfriNIC data is *tiny* compared to something like the RIPE data set and the code isn't optimised for processing that many objects. I'll see if I get the time this weekend to see what else I can mine outta the data with optimised code. Thanks Andrew On Fri, Oct 24, 2025 at 6:03?PM brian at ctnmw.net wrote: > Hi Andrew, > > This is an excellent resource, great work! I have a client who runs a > geo-location business that is several factors better in terms of pinpoint > accuracy than most. I think we would find some very interesting results if > we ran this dataset through their API?. > > Should I check with them whether this can be done affordably (or pro bono)? > > Thanks, > > Brian > > ? > Brian Munyao Longwe | CEO > > E: brian at ctnmw.net | www.ctnmw.net | @convergedmalawi > A: #744, Area 47, Sector 4, Lilongwe, Malawi > Skype: blongwe > M: +265 999708883 | +265 883571553 > > > > > On 24 Oct 2025, at 12:45?PM, Andrew Alston wrote: > > Hi All, > > While I haven't got around to publishing the code behind this - mainly > because it by necessity exposes certain data and requires a BGP dump from a > juniper router which is hundreds of megs big, I've attached the output of > the code I wrote. > > One caveat with this data - There is nothing inherently wrong with space > allocated to an organisation being announced by a non-AfriNIC ASN, there > are many legitimate cases and reasons behind this. The same thing happens > when space is allocated to one organisation but announced by another, and > this can happen when a sub-company of a parent company is announcing space > from their own ASN when the space was originally allocated to the parent. > As such, when reading this data, it's important to understand that the > abnormalities detected do not necessarily indicate anything nefarious - and > this data should not be seen as accusations of malfeasance against anyone. > > Let's see if the lists let this post through! > > Thanks > > Andrew > > _______________________________________________ > Members-Discuss mailing list > Members-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/members-discuss > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Fri Oct 24 15:28:39 2025 From: owen at delong.com (Owen DeLong) Date: Fri, 24 Oct 2025 08:28:39 -0700 Subject: [rpd] AfriNIC audit data In-Reply-To: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> References: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> Message-ID: <3136DB2F-1585-456B-A1A7-E8540B1D879B@delong.com> > On Oct 24, 2025, at 06:11, Fernando Frediani wrote: > > ?Yes there are legitimate cases, but when this happens it may be a signal of alert. The point is to find two things: 1) If the ASN announcing it doesn't have any relation to the resource holder and 2) If resources are being used out of the region (the worst). There are many legitimate reasons for 1. There is nothing in AfriNIC policy to prohibit 2 unless the space was issued after the soft landing policy was triggered, so that?s also legitimate for the vast majority of AfriNIC issued space. > For the case of parent/sub-company ideally resources should be transferred among companies using them in reality then. No such requirement exists in policy or bylaws. You don?t get to just make up rules as you go along or attempt to enforce rules that aren?t on the books just because they fit your particular sense of morality. Attempts to do so are how AfriNIC got itself into the previous large mess. Owen > > Fernando > >> On 10/24/2025 7:45 AM, Andrew Alston wrote: >> Hi All, >> >> While I haven't got around to publishing the code behind this - mainly because it by necessity exposes certain data and requires a BGP dump from a juniper router which is hundreds of megs big, I've attached the output of the code I wrote. >> >> One caveat with this data - There is nothing inherently wrong with space allocated to an organisation being announced by a non-AfriNIC ASN, there are many legitimate cases and reasons behind this. The same thing happens when space is allocated to one organisation but announced by another, and this can happen when a sub-company of a parent company is announcing space from their own ASN when the space was originally allocated to the parent. As such, when reading this data, it's important to understand that the abnormalities detected do not necessarily indicate anything nefarious - and this data should not be seen as accusations of malfeasance against anyone. >> >> Let's see if the lists let this post through! >> >> Thanks >> >> Andrew >> >> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd From owen at delong.com Fri Oct 24 15:34:19 2025 From: owen at delong.com (Owen DeLong) Date: Fri, 24 Oct 2025 08:34:19 -0700 Subject: [rpd] AfriNIC audit data In-Reply-To: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> References: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> Message-ID: <439CA1AB-5956-4048-8831-5A244AB36F12@delong.com> An HTML attachment was scrubbed... URL: From fhfrediani at gmail.com Fri Oct 24 15:36:24 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Fri, 24 Oct 2025 12:36:24 -0300 Subject: [rpd] AfriNIC audit data In-Reply-To: <3136DB2F-1585-456B-A1A7-E8540B1D879B@delong.com> References: <4ff3cf61-1c3c-46bc-b45e-4ba4d2f9b1e2@gmail.com> <3136DB2F-1585-456B-A1A7-E8540B1D879B@delong.com> Message-ID: <46523f07-638d-45d1-9a71-40228db12e47@gmail.com> On 10/24/2025 12:28 PM, Owen DeLong wrote: > No such requirement exists in policy or bylaws. You don?t get to just make up rules as you go along or attempt to enforce rules that aren?t on the books just because they fit your particular sense of morality. > > Attempts to do so are how AfriNIC got itself into the previous large mess. That's why I mentioned 'ideally' but you ignored it solemnly so that you could deliver your speeches as usual. > > Owen > >> Fernando >> >>> On 10/24/2025 7:45 AM, Andrew Alston wrote: >>> Hi All, >>> >>> While I haven't got around to publishing the code behind this - mainly because it by necessity exposes certain data and requires a BGP dump from a juniper router which is hundreds of megs big, I've attached the output of the code I wrote. >>> >>> One caveat with this data - There is nothing inherently wrong with space allocated to an organisation being announced by a non-AfriNIC ASN, there are many legitimate cases and reasons behind this. The same thing happens when space is allocated to one organisation but announced by another, and this can happen when a sub-company of a parent company is announcing space from their own ASN when the space was originally allocated to the parent. As such, when reading this data, it's important to understand that the abnormalities detected do not necessarily indicate anything nefarious - and this data should not be seen as accusations of malfeasance against anyone. >>> >>> Let's see if the lists let this post through! >>> >>> Thanks >>> >>> Andrew >>> >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd From fhfrediani at gmail.com Fri Oct 24 15:38:39 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Fri, 24 Oct 2025 12:38:39 -0300 Subject: [rpd] AfriNIC audit data In-Reply-To: <439CA1AB-5956-4048-8831-5A244AB36F12@delong.com> References: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> <439CA1AB-5956-4048-8831-5A244AB36F12@delong.com> Message-ID: <310e5ed2-a1f5-45cf-908f-0e11aa4c8535@gmail.com> On 10/24/2025 12:34 PM, Owen DeLong wrote: > > > If they said that, they were mistaken. Reread the policy documents and > the bylaws. No such requirement exists in the actual written rules. > > It may cause you moral outrage or feel wrong to you, but it is not > against the actual written rules. Multiple attempts to change that > have failed to gain consensus over the years. The record is pretty clear. I understand that possibility can be quiet bad for business like brokerage or those who lease IP space or people not caring much on how the resources destined to be used to develop internet em Africa are used in a different way > > Owen > >> >>> >>> >>> >>> On Fri, Oct 24, 2025 at 4:39?PM Fernando Frediani >>> wrote: >>> >>> >>> On Fri, 24 Oct 2025, 10:18 Andrew Alston, >>> wrote: >>> >>> >>> With regards to space being used out of region - that's >>> extremely difficult to actually know - because the BGP table >>> has no knowledge of geography :) >>> >>> >>> I wouldn't say it is trivial but with geolocation data plus some >>> traveroutes and latency check it is not extremelly dificult to >>> find out. >>> >>> With some intended work that can be found out and further >>> investigate to give AfriNic all necessary information. >>> >>> Fernanso >>> >>> >>> On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani >>> wrote: >>> >>> Yes there are legitimate cases, but when this happens it >>> may be a signal >>> of alert. The point is to find two things: 1) If the ASN >>> announcing it >>> doesn't have any relation to the resource holder and 2) >>> If resources are >>> being used out of the region (the worst). >>> For the case of parent/sub-company ideally resources >>> should be >>> transferred among companies using them in reality then. >>> >>> Fernando >>> >>> On 10/24/2025 7:45 AM, Andrew Alston wrote: >>> > Hi All, >>> > >>> > While I haven't got around to publishing the code >>> behind this - mainly >>> > because it by necessity exposes certain data and >>> requires a BGP dump >>> > from a juniper router which is hundreds of megs big, >>> I've attached the >>> > output of the code I wrote. >>> > >>> > One caveat with this data - There is nothing >>> inherently wrong with >>> > space allocated to an organisation being announced by >>> a non-AfriNIC >>> > ASN, there are many legitimate cases and reasons >>> behind this.? The >>> > same thing happens when space is allocated to one >>> organisation but >>> > announced by another, and this can happen when a >>> sub-company of a >>> > parent company is announcing space from their own ASN >>> when the space >>> > was originally allocated to the parent. As such, when >>> reading this >>> > data, it's important to understand that the >>> abnormalities?detected do >>> > not necessarily indicate anything nefarious - and this >>> data should not >>> > be seen as accusations of malfeasance?against anyone. >>> > >>> > Let's see if the lists let this post through! >>> > >>> > Thanks >>> > >>> > Andrew >>> > >>> > >>> > _______________________________________________ >>> > RPD mailing list >>> > RPD at afrinic.net >>> > https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From jaco at uls.co.za Sat Oct 25 06:34:16 2025 From: jaco at uls.co.za (Jaco Kroon) Date: Sat, 25 Oct 2025 08:34:16 +0200 Subject: [rpd] AfriNIC audit data In-Reply-To: <439CA1AB-5956-4048-8831-5A244AB36F12@delong.com> References: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> <439CA1AB-5956-4048-8831-5A244AB36F12@delong.com> Message-ID: Hi, On 2025/10/24 17:34, Owen DeLong via RPD wrote: > On Oct 24, 2025, at 08:06, Fernando Frediani wrote: > >> ? >> On 10/24/2025 11:02 AM, Andrew Alston wrote: >>> You also have to remember, that space allocated prior to >>> soft-landing has no geographic restrictions on where it can be used >>> - geographic restrictions only applied to space allocated under soft >>> landing. >> >> Don't remember of this being like that. Resources registered in >> AfriNic region, regardless of when they were assigned are to be used >> majority within the region for Africa Internet development and >> AfriNic staff already made that clear in the past. There would be no >> sense to get resources from AfriNic and be able to freely use outside >> the region. >> > If they said that, they were mistaken. Reread the policy documents and > the bylaws. No such requirement exists in the actual written rules. > > It may cause you moral outrage or feel wrong to you, but it is not > against the actual written rules. Multiple attempts to change that > have failed to gain consensus over the years. The record is pretty clear. That's debatable, but I do believe Fernando isn't wrong, from our own RSA pre-dating a LOT of the current outrage and unhappiness and debate and court proceedings etc etc .... so this may throw further fuel, but let's state for the record what's in the contracts around the points of contention I can think of right now.? Please keep in mind I'm not a lawyer, so the usual caveats and disclaimers apply here.? This is my own layman's reading of the relevant sections. *Leasing of IP space*: "4. Conditions of service (c) Applicant's use of the services The Applicant hereby irrevocably: (i) Commits itself to using the services solely for the purpose for which it was requested." Since leasing of IP space was never a legitimate purpose for requesting resources, the above in my humble opinion irrevocably precludes leasing of resources as a legitimate use, and anyone leasing IP space should technically return that space to AFRINIC for re-distribution, sell it, or simply not use it, but that goes against other points of both the RSA and the CPM which I *recall* but don't intend to dig up right now which from memory boils down to any resources that you're not actively using, or can't reasonably use within a 12-month (if I recall correctly) period must be returned to AFRINIC.? This also implies that if you BUY resources from another afrinic member you should be in a position to reasonably use that within 12 months or you're just going to be the one having to return it.? Regardless 6(d)(iv) transfer of the number resources is strictly prohibited ... but this has changed with more recent policies. *Enforcing of new rules retrospectively*: 1 Preamble (b) AFRINIC, in the light of the foregoing, reserves itself the right to amend this agreement partially or otherwise where it is so mandated by its Board after giving notice to its members. Such amendment(s) where effected, will take effect after the lapse of 30 days following its/their posting on its website and to the members mailing list. As such, things *can* be fixed retroactively.? But it also permits abuse of power, so it's a powerful clause that could potentially be abused by those in the Board specifically (Afrinic does NOT have the power to unilaterally change the agreement unless mandated by the board - is my reading of the above). *In region vs out-of-region use*: "1 Preamble (a) AFRINIC, the African Network Information Center is the regional Internet registry for Africa and the Indian Ocean region and is: (i) the entity accredited by ICANN under the ICP-2 policy 2 (Resolution 05.25 of May 2005) to assign Internet number resources *within*?the region;" This is a bit more sticky ... the intent seems to be to state that resources are for use in the region, but it is unclear if the entity merely needs to be head quartered in the region, or has to use the resources in the region.? Lawyers will likely have a field day (decade) based on this one. Combining this with sections from the CPM (emphasis added): "4.0 Internet Number Resources are distributed in a hierarchical structure in which IANA (The Internet Assigned Numbers Authority) allocates blocks of number resources *to AFRINIC*, to be redistributed *throughout the African region*. AFRINIC redistributes to its members and also delegates to them the authority to make assignments and *sub-allocations to customers* where appropriate and *in accordance with the policies and procedures described in this document*." So the resources has to be distributed throughout the *African* region, not the world or other regions, and the customers (members) of AFRINIC then does the same, bound by the same policies (ie, also throughout the African region). So I do agree that there is reason for debate as to historice in-region vs out-of-region use, but to me it's clear that the intent was at least for "primarily used in the african region". Will have to let the lawyers have at this one ... there is definitely ambiguity so let's hope that the plain and obvious *intent* wins out. On the other hand ... I think it's time to let IPv4 burn and those not ready for v6 will eventually get disconnected from the rest of us who are ready. Kind regards, Jaco > > Owen > >> >>> >>> >>> >>> On Fri, Oct 24, 2025 at 4:39?PM Fernando Frediani >>> wrote: >>> >>> >>> On Fri, 24 Oct 2025, 10:18 Andrew Alston, >>> wrote: >>> >>> >>> With regards to space being used out of region - that's >>> extremely difficult to actually know - because the BGP table >>> has no knowledge of geography :) >>> >>> >>> I wouldn't say it is trivial but with geolocation data plus some >>> traveroutes and latency check it is not extremelly dificult to >>> find out. >>> >>> With some intended work that can be found out and further >>> investigate to give AfriNic all necessary information. >>> >>> Fernanso >>> >>> >>> On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani >>> wrote: >>> >>> Yes there are legitimate cases, but when this happens it >>> may be a signal >>> of alert. The point is to find two things: 1) If the ASN >>> announcing it >>> doesn't have any relation to the resource holder and 2) >>> If resources are >>> being used out of the region (the worst). >>> For the case of parent/sub-company ideally resources >>> should be >>> transferred among companies using them in reality then. >>> >>> Fernando >>> >>> On 10/24/2025 7:45 AM, Andrew Alston wrote: >>> > Hi All, >>> > >>> > While I haven't got around to publishing the code >>> behind this - mainly >>> > because it by necessity exposes certain data and >>> requires a BGP dump >>> > from a juniper router which is hundreds of megs big, >>> I've attached the >>> > output of the code I wrote. >>> > >>> > One caveat with this data - There is nothing >>> inherently wrong with >>> > space allocated to an organisation being announced by >>> a non-AfriNIC >>> > ASN, there are many legitimate cases and reasons >>> behind this.? The >>> > same thing happens when space is allocated to one >>> organisation but >>> > announced by another, and this can happen when a >>> sub-company of a >>> > parent company is announcing space from their own ASN >>> when the space >>> > was originally allocated to the parent. As such, when >>> reading this >>> > data, it's important to understand that the >>> abnormalities?detected do >>> > not necessarily indicate anything nefarious - and this >>> data should not >>> > be seen as accusations of malfeasance?against anyone. >>> > >>> > Let's see if the lists let this post through! >>> > >>> > Thanks >>> > >>> > Andrew >>> > >>> > >>> > _______________________________________________ >>> > RPD mailing list >>> > RPD at afrinic.net >>> > https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Sat Oct 25 18:08:56 2025 From: owen at delong.com (Owen DeLong) Date: Sat, 25 Oct 2025 11:08:56 -0700 Subject: [rpd] AfriNIC audit data In-Reply-To: References: Message-ID: <04DAFA9C-B454-4802-8107-0377D1F596CF@delong.com> An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Mon Oct 27 00:01:25 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Mon, 27 Oct 2025 00:01:25 +0000 Subject: [rpd] Whois DB part of RPD ? Message-ID: <6369B1D1-86FB-4BF5-B385-674F4AEF3891@hevis.co.za> Good day, As I?m (again) wanting to make changes similar to RIPE DB, that seems to be in need of manual/hostmaster intervention from AfriNIC, I?m wondering where do we discuss/request updates to the Whois DB?s operations and policies w.r.t. who can/should-be-able-to make what changes? Most of the WHOIS db manuals are like circa 2005 documentation --- Hendrik Visage Director - HeViS.Co Systems Pty Ltd T/A Envisage Cloud Solutions Mobile: +27-84-612-5345 hvisage at hevis.co.za hvisage at envisage.co.za Instant messaging: https://t.me/hvisage --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From baya.sylvain at cmnog.cm Mon Oct 27 00:24:19 2025 From: baya.sylvain at cmnog.cm (Sylvain BAYA) Date: Mon, 27 Oct 2025 01:24:19 +0100 Subject: [rpd] Whois DB part of RPD ? In-Reply-To: <6369B1D1-86FB-4BF5-B385-674F4AEF3891@hevis.co.za> References: <6369B1D1-86FB-4BF5-B385-674F4AEF3891@hevis.co.za> Message-ID: <2f0e0309-dcec-4154-92ff-02b9cc0e0f29@cmnog.cm> Le 27/10/2025 ? 01:01, Hendrik Visage a ?crit?: > Good day, > > ?As I?m (again) wanting to make changes similar to RIPE DB, that seems > to be in need of manual/hostmaster intervention from AfriNIC, I?m > wondering where do we discuss/request updates to the Whois DB?s > operations and policies w.r.t. who can/should-be-able-to make what > changes? > Hi Hendrik, The Whois DBWG is here: https://lists.afrinic.net/mailman/listinfo/dbwg ...so, its archive: DBWG Archives Also: AFRINIC Database Working Group https://afrinic.net/community/working-groups/dbwg Hope this helps! Shalom, --sb. > > > ?Most of the WHOIS db manuals are like circa 2005 documentation > > --- > Hendrik Visage > Director - HeViS.Co Systems Pty Ltd > T/A ?Envisage Cloud Solutions > Mobile: +27-84-612-5345 > hvisage at hevis.co.za > hvisage at envisage.co.za > Instant messaging: https://t.me/hvisage > > > --- > > Hendrik Visage > > hvisage at hevis.co.za > > > HeViS.Co Systems Pty Ltd > > https://www.envisage.co.za > > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd -- Best Regards ! baya.sylvain [AT cmNOG DOT cm] | cmNOG's Structure | CAMIX's Website | Douala-IX's Looking Glass | cmNOG's Surveys | Subscribe to cmNOG's Mailing List | __ #LASAINTEBIBLE|#Eph?siens3:17,14-19?17 en sorte que CHRIST habite dans vos c?urs par la foi; afin qu'?tant enracin?s et fond?s dans L'Amour,?#AMEN,#Maranatha,#MerciJ?SUS! #?MaPri?re? est que tu naisses de nouveau.#Chr?tiennement? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x0387408365AC8594.asc Type: application/pgp-keys Size: 14591 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From hvisage at hevis.co.za Mon Oct 27 12:33:00 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Mon, 27 Oct 2025 12:33:00 +0000 Subject: [rpd] Whois DB part of RPD ? In-Reply-To: <2f0e0309-dcec-4154-92ff-02b9cc0e0f29@cmnog.cm> References: <6369B1D1-86FB-4BF5-B385-674F4AEF3891@hevis.co.za> <2f0e0309-dcec-4154-92ff-02b9cc0e0f29@cmnog.cm> Message-ID: <8A905470-2CDD-40E3-9D5F-A34D0016FF58@hevis.co.za> On 27 Oct 2025, at 02:24, Sylvain BAYA wrote: Le 27/10/2025 ? 01:01, Hendrik Visage a ?crit : Good day, As I?m (again) wanting to make changes similar to RIPE DB, that seems to be in need of manual/hostmaster intervention from AfriNIC, I?m wondering where do we discuss/request updates to the Whois DB?s operations and policies w.r.t. who can/should-be-able-to make what changes? Hi Hendrik, The Whois DBWG is here: https://lists.afrinic.net/mailman/listinfo/dbwg ...so, its archive: DBWG Archives Also: AFRINIC Database Working Group https://afrinic.net/community/working-groups/dbwg Hope this helps! Thank you!! --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregoire.ehoumi at yahoo.fr Wed Oct 29 12:22:58 2025 From: gregoire.ehoumi at yahoo.fr (=?utf-8?Q?Gr=C3=A9goire_EHOUMI?=) Date: Wed, 29 Oct 2025 08:22:58 -0400 Subject: [rpd] AfriNIC audit data In-Reply-To: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> References: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> Message-ID: An HTML attachment was scrubbed... URL: From fhfrediani at gmail.com Wed Oct 29 13:24:09 2025 From: fhfrediani at gmail.com (Fernando Frediani) Date: Wed, 29 Oct 2025 10:24:09 -0300 Subject: [rpd] AfriNIC audit data In-Reply-To: References: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> Message-ID: <87e1d2da-0351-45ae-9a37-b1ffc482fc82@gmail.com> Hello Just wanted to share AfriNic's goal to serve Africa from AfriNic bylaws: "3.4) The Company shall have, both within and outside the Republic of Mauritius, full capacity to carry and/or undertake any business or activity, including but not limited to the following objects: ? ? i. to provide the service of allocating and registering Internet resources for the purposes of enabling communications via open system network protocols and to assist in the development and growth of the Internet in the African region;" Fernando On 10/29/2025 9:22 AM, Gr?goire EHOUMI wrote: > Hi Fernando, >> >> Don't remember of this being like that. Resources registered in >> AfriNic region, regardless of when they were assigned are to be used >> majority within the region for Africa Internet development and >> AfriNic staff already made that clear in the past. There would be no >> sense to get resources from AfriNic and be able to freely use outside >> the region. >> > You are right. We had these discussions several times in the past. It > is a Regional Internet Registry and its resources are to be used in > the region. Members in the region which span multiple regions should > establish relationship with multiple RIRs. Staff in the evaluation of > requests might allow some out of region usage of resources if and when > the relationship with other RIRs not possible. The type of custodian > at AFRINIC is of "Valid as long as original criteria remain > satisfied". If staff has allowed out of region usage, audit should not > find problems. > The two policy proposals which tried to define which proportion of > resource may be used out of the region failed for the reasons above > and also because the AFRINIC held resources are not for sale. > > https://afrinic.net/policy/archive/limited-out-of-region-allocation-of-ipv4-resources-afpub-2011-v4-003-draft-02 > > > https://afrinic.net/policy/archive/out-of-region-use-of-afrinic-internet-number-resources > > Thanks > Gr?goire > > > >>> >>> >>> >>> On Fri, Oct 24, 2025 at 4:39?PM Fernando Frediani >>> wrote: >>> >>> >>> On Fri, 24 Oct 2025, 10:18 Andrew Alston, >>> wrote: >>> >>> >>> With regards to space being used out of region - that's >>> extremely difficult to actually know - because the BGP table >>> has no knowledge of geography :) >>> >>> >>> I wouldn't say it is trivial but with geolocation data plus some >>> traveroutes and latency check it is not extremelly dificult to >>> find out. >>> >>> With some intended work that can be found out and further >>> investigate to give AfriNic all necessary information. >>> >>> Fernanso >>> >>> >>> On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani >>> wrote: >>> >>> Yes there are legitimate cases, but when this happens it >>> may be a signal >>> of alert. The point is to find two things: 1) If the ASN >>> announcing it >>> doesn't have any relation to the resource holder and 2) >>> If resources are >>> being used out of the region (the worst). >>> For the case of parent/sub-company ideally resources >>> should be >>> transferred among companies using them in reality then. >>> >>> Fernando >>> >>> On 10/24/2025 7:45 AM, Andrew Alston wrote: >>> > Hi All, >>> > >>> > While I haven't got around to publishing the code >>> behind this - mainly >>> > because it by necessity exposes certain data and >>> requires a BGP dump >>> > from a juniper router which is hundreds of megs big, >>> I've attached the >>> > output of the code I wrote. >>> > >>> > One caveat with this data - There is nothing >>> inherently wrong with >>> > space allocated to an organisation being announced by >>> a non-AfriNIC >>> > ASN, there are many legitimate cases and reasons >>> behind this.? The >>> > same thing happens when space is allocated to one >>> organisation but >>> > announced by another, and this can happen when a >>> sub-company of a >>> > parent company is announcing space from their own ASN >>> when the space >>> > was originally allocated to the parent. As such, when >>> reading this >>> > data, it's important to understand that the >>> abnormalities?detected do >>> > not necessarily indicate anything nefarious - and this >>> data should not >>> > be seen as accusations of malfeasance?against anyone. >>> > >>> > Let's see if the lists let this post through! >>> > >>> > Thanks >>> > >>> > Andrew >>> > >>> > >>> > _______________________________________________ >>> > RPD mailing list >>> > RPD at afrinic.net >>> > https://lists.afrinic.net/mailman/listinfo/rpd >>> >>> _______________________________________________ >>> RPD mailing list >>> RPD at afrinic.net >>> https://lists.afrinic.net/mailman/listinfo/rpd >>> >> _______________________________________________ >> RPD mailing list >> RPD at afrinic.net >> https://lists.afrinic.net/mailman/listinfo/rpd -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at alstonnetworks.net Wed Oct 29 14:15:47 2025 From: aa at alstonnetworks.net (Andrew Alston) Date: Wed, 29 Oct 2025 17:15:47 +0300 Subject: [rpd] AfriNIC audit data In-Reply-To: <87e1d2da-0351-45ae-9a37-b1ffc482fc82@gmail.com> References: <89c811ff-4c47-4756-a670-45d8ee1b14d0@gmail.com> <87e1d2da-0351-45ae-9a37-b1ffc482fc82@gmail.com> Message-ID: Read the wording carefully. A.) note the ?including but not limited to? B.) note that ?to provide the service of allocating and registering Internet resources for the purpose of enabling communications via open system network protocols? is distinct from the second half of the sentence - which is why there it says ?and? there. The bylaws do not prohibit the allocation of space for off continent usage - nor does any policy outside of the soft landing policy. As people have pointed out - every attempt to do this via policy has not gained consensus. I am not advocating for space to be allocated and used off continent btw, I am merely stating the current status quo - and if indeed people are using resources off continent within the bounds of policy set by the policy process, then we are contributors to the policy process have only ourselves to blame. But let?s not try and twist the words of the bylaws and other things to say things they dont say - because it?s exactly this kind of thing that can end up with the organisation in legal trouble when they apply meaning to wording that isn?t there Andrew > "3.4) The Company shall have, both within and outside the Republic of > Mauritius, full capacity to carry and/or undertake any business or > activity, including but not limited to the following objects: > > i. to provide the service of allocating and registering Internet > resources for the purposes of enabling communications via open system > network protocols and to assist in the development and growth of the > Internet in the African region;" > > Fernando > On 10/29/2025 9:22 AM, Gr?goire EHOUMI wrote: > > Hi Fernando, > > Don't remember of this being like that. Resources registered in AfriNic > region, regardless of when they were assigned are to be used majority > within the region for Africa Internet development and AfriNic staff already > made that clear in the past. There would be no sense to get resources from > AfriNic and be able to freely use outside the region. > > You are right. We had these discussions several times in the past. It is a > Regional Internet Registry and its resources are to be used in the region. > Members in the region which span multiple regions should establish > relationship with multiple RIRs. Staff in the evaluation of requests might > allow some out of region usage of resources if and when the relationship > with other RIRs not possible. The type of custodian at AFRINIC is of "Valid > as long as original criteria remain satisfied". If staff has allowed out of > region usage, audit should not find problems. > > The two policy proposals which tried to define which proportion of > resource may be used out of the region failed for the reasons above and > also because the AFRINIC held resources are not for sale. > > > https://afrinic.net/policy/archive/limited-out-of-region-allocation-of-ipv4-resources-afpub-2011-v4-003-draft-02 > > > > https://afrinic.net/policy/archive/out-of-region-use-of-afrinic-internet-number-resources > > Thanks > Gr?goire > > > > > > > > On Fri, Oct 24, 2025 at 4:39?PM Fernando Frediani > wrote: > >> >> On Fri, 24 Oct 2025, 10:18 Andrew Alston, wrote: >> >>> >>> With regards to space being used out of region - that's extremely >>> difficult to actually know - because the BGP table has no knowledge of >>> geography :) >>> >> >> I wouldn't say it is trivial but with geolocation data plus some >> traveroutes and latency check it is not extremelly dificult to find out. >> >> With some intended work that can be found out and further investigate to >> give AfriNic all necessary information. >> >> Fernanso >> >>> >>> On Fri, Oct 24, 2025 at 4:11?PM Fernando Frediani >>> wrote: >>> >>>> Yes there are legitimate cases, but when this happens it may be a >>>> signal >>>> of alert. The point is to find two things: 1) If the ASN announcing it >>>> doesn't have any relation to the resource holder and 2) If resources >>>> are >>>> being used out of the region (the worst). >>>> For the case of parent/sub-company ideally resources should be >>>> transferred among companies using them in reality then. >>>> >>>> Fernando >>>> >>>> On 10/24/2025 7:45 AM, Andrew Alston wrote: >>>> > Hi All, >>>> > >>>> > While I haven't got around to publishing the code behind this - >>>> mainly >>>> > because it by necessity exposes certain data and requires a BGP dump >>>> > from a juniper router which is hundreds of megs big, I've attached >>>> the >>>> > output of the code I wrote. >>>> > >>>> > One caveat with this data - There is nothing inherently wrong with >>>> > space allocated to an organisation being announced by a non-AfriNIC >>>> > ASN, there are many legitimate cases and reasons behind this. The >>>> > same thing happens when space is allocated to one organisation but >>>> > announced by another, and this can happen when a sub-company of a >>>> > parent company is announcing space from their own ASN when the space >>>> > was originally allocated to the parent. As such, when reading this >>>> > data, it's important to understand that the abnormalities detected do >>>> > not necessarily indicate anything nefarious - and this data should >>>> not >>>> > be seen as accusations of malfeasance against anyone. >>>> > >>>> > Let's see if the lists let this post through! >>>> > >>>> > Thanks >>>> > >>>> > Andrew >>>> > >>>> > >>>> > _______________________________________________ >>>> > RPD mailing list >>>> > RPD at afrinic.net >>>> > https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>>> _______________________________________________ >>>> RPD mailing list >>>> RPD at afrinic.net >>>> https://lists.afrinic.net/mailman/listinfo/rpd >>>> >>> _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > > _______________________________________________ > RPD mailing list > RPD at afrinic.net > https://lists.afrinic.net/mailman/listinfo/rpd > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvisage at hevis.co.za Wed Oct 29 18:57:50 2025 From: hvisage at hevis.co.za (Hendrik Visage) Date: Wed, 29 Oct 2025 18:57:50 +0000 Subject: [rpd] Pushing IPv6 ? (CloudFlare CGNAT blog post) In-Reply-To: <9DF19C1D-9F62-4AD7-B35E-9CA4BB35E819@delong.com> References: <30A65637-790B-45E7-9213-D3BAC3720F77@hevis.co.za> <069b88a9-0762-479d-84cf-de4eed64520c@uls.co.za> <9DF19C1D-9F62-4AD7-B35E-9CA4BB35E819@delong.com> Message-ID: <01049981-8C45-499A-9500-8B39C28648A7@hevis.co.za> So Cloudflare wrote a blog post... >> My concern is getting CG-NAT just right is non-trivial, as anybody that provides services even marginally more complex than http will attest to. And given the above situation where hosting providers are reluctant to deploy IPv6 for some reason. > NAT of any form is a horrible ugly hack that has consistently and for all time it has existed provided more pain than good. If we don?t get provider off the stick to provide IPv6, CG-NAT is the future we will be stuck with. Worse, it?s going to likely be multi-layer CG-NAT and it?s only going to get uglier the longer we preserve the fallacious illusion that IPv4 must be the lingua franca of the internet and all sites must support v4 and v6 is optional. https://blog.cloudflare.com/detecting-cgn-to-reduce-collateral-damage/ Archived: https://web.archive.org/web/20251029155338/https://blog.cloudflare.com/detecting-cgn-to-reduce-collateral-damage/ It contains an interesting graph: https://web.archive.org/web/20251029155343im_/https://cf-assets.www.cloudflare.com/zkvhlag99gkb/2YBdqPx0ALt7pY7rmQZyLQ/049922bae657a715728700c764c4af16/BLOG-3046_2.png To visualize the IPv4 allocation gap, we plot country-level ratios of users to IP addresses in the figure below. We take online user estimates from the World Bank Group and the number of IP addresses in a country from Regional Internet Registry (RIR) records. The colour-coded map that emerges shows that the usage of each IP address is more concentrated in regions that generally have poor Internet penetration. For example, large portions of Africa and South Asia appear with the highest user-to-IP ratios. Frankly speaking: 800k IPs is NOT going to make that dark blue Africa anything barely orange? never mind the yellow? and ironically, the yellow parts have the highest IPv6 deployments/usage. Time to let go of the IPv4 space so we can seriously leave that behind and push for IPv6 The scarcity of IPv4 address space means that regional differences can only worsen as Internet penetration rates increase. A natural consequence of increased demand in developing regions is that ISPs would rely even more heavily on CGNAT, and is compounded by the fact that CGNAT is common in mobile networks that users in developing regions so heavily depend on. All of this means that actions known to be based on IP reputation or behaviour would disproportionately affect developing economies. --- Hendrik Visage hvisage at hevis.co.za HeViS.Co Systems Pty Ltd https://www.envisage.co.za From owen at delong.com Wed Oct 29 19:01:50 2025 From: owen at delong.com (Owen DeLong) Date: Wed, 29 Oct 2025 12:01:50 -0700 Subject: [rpd] AfriNIC audit data In-Reply-To: <87e1d2da-0351-45ae-9a37-b1ffc482fc82@gmail.com> References: <87e1d2da-0351-45ae-9a37-b1ffc482fc82@gmail.com> Message-ID: <799E8020-C873-4EC9-8FA4-9EE7ED84CBAF@delong.com> An HTML attachment was scrubbed... URL: