November 2020 - Test - lists.nanog.org

AFRINIC IP Block Thefts -- The Saga Continues
by Ronald F. Guilmette 18 Nov '20

18 Nov '20

South African tech journalist Jan Vermeulen has written a new chapter in this ongoing saga of greed, theft, and skulduggery. EXECUTIVE SUMMARY: Maikel Uerlings and Elad Cohen registered a bunch of new domain names as part of their overall scheme to steal AFRINIC legacy blocks by fiddling the AFRINIC WHOIS records for the contact persons for each legacy block that they wanted to steal. The domain names themselves were deliberately chosen and tailored to try to minimize suspicion relating to their numerous legacy block thefts. https://mybroadband.co.za/news/security/367188-the-great-african-ip-address… How exactly these two gentlemen managed to gain the kind of read/write access to the AFRINIC WHOIS data base which allowed them to fiddle so many WHOIS records for so many AFRINIC legacy IPv4 blocks is something that AFRINIC has yet to offer any explanation for, even a full year after these thefts came to light. NOTE: As of the present moment AFRINIC is *still* delegating authority for reverse DNS for many of the stolen legacy blocks detailed in Jan's most recent article to name servers that are owned and controled by Maikel Uerlings and/or Elad Cohen. In particular, Uerlings and/or Cohen are still in control of the reverse DNS for all of the stolen legacy blocks listed in the table below, as well as the reverse DNS for the very valuable 196.16.0.0/14 block, worth well over $5 million USD. There is no reasonable excuse for this ongoing inaction by AFRINIC. As things stand, it appears that AFRINIC is still refusing to do even the minimum amount necessary to stop the profiteering of Uerlings and Cohen, EVEN THOUGH every additional dollar, every additional sheckel, and every additional ruble that they earn from these ongoing thefts is being used to fund Cohen's ongoing lawsuit against AFRINIC. AFRINIC has known about these legacy block thefts for well over a year now, and yet in all this time AFRINIC has done absolutely nothing to remediate the fradulent entries in their WHOIS data base, or to remove the reverse DNS relegations for the 196.16.0.0/14 block and the several stolen blocks listed below. Reasonable people can and should ask why. One theory, currently circulating among people I know is that Mr. Uerlings and/or Mr. Cohen are in possession of some confidential information that AFRINIC really hopes will never see the light of day, and that AFRINIC is being blackmailed into inaction. Whatever the reason, AFRINIC's continuing inaction is effectively providing funding for Mr. Cohen's ongoing lawsuit against AFRINIC. How this makes any sense at all is something that remains for AFRINIC to explain. #------------------------------------------------------------------------ # ORG: (SC) ORG-AISL1-AFRINIC "AECI Information Services (Pty) Ltd" #------------------------------------------------------------------------ 168.80.0.0/15 #------------------------------------------------------------------------ # ORG: (ZA) ORG-AA79-AFRINIC "Agrihold" #------------------------------------------------------------------------ 163.198.0.0/16 #------------------------------------------------------------------------ # ORG: (ZA) ORG-ACSL2-AFRINIC "Affiliated Computing Services (Pty) Ltd" #------------------------------------------------------------------------ 160.116.0.0/16 #------------------------------------------------------------------------ # ORG: (ZA) ORG-FSED1-AFRINIC "Free State Education Department" #------------------------------------------------------------------------ 168.76.0.0/19 168.76.36.0/24 168.76.128.0/20 168.76.144.0/22 168.76.148.0/24 168.76.228.0/22 168.76.232.0/21 168.76.240.0/20 #------------------------------------------------------------------------ # ORG: (ZA) ORG-SCS1-AFRINIC "Safren Computer Services" #------------------------------------------------------------------------ 155.159.0.0/16

12 17

Fwd: Phoenix-IX Contact
by Paul Emmons 17 Nov '20

17 Nov '20

still trying to post . . . -------- Forwarded Message -------- Subject: Re: Phoenix-IX Contact Date: Mon, 16 Nov 2020 13:15:34 -0700 From: Paul Emmons <paul(a)iosaz.net> To: nanog(a)nanog.org Hello All! I've been out of the loop here and but have some updates. There was a change last spring and I moved on to other projects. But that hasn't worked out for the IX. I have regained access to all of the elements, including the email and voip. Let me reach out to each of you offline in the coming days. I have been able to reach out to a few locals that are willing to help get the project back up to where it needs to be. If I haven;t reached out to you in the next 48 hours or you have something urgent, please reach out to me here (my personal email) or via the Phoenix-IX Contacts peering(a)phoenix-ix.net +1 602 688-6414 ~Paul Emmons On 11/16/2020 12:23 PM, Neil Hanlon wrote: > While I agree it is objectively irresponsible to abandon a project > without passing it to another, I think that possibly in this situation > we don't know all the details? > > 2020 has been a difficult year for everyone. Perhaps Paul (and > whomever else may be responsible for Phoenix-IX) were subject to > things this year beyond their control which led them to be unable to > work on the project and unable to transfer it, either.. unfortunate, > yes.. but not malicious surely. > > If Paul _is_ reading these messages.. I think support is the best path > forward.. If there are things that can be done to assist/take over the > IX... maybe that would help (as you, Kate, had offered towards the > beginning of this all). Though of course, the first step is _reaching_ > them... Maybe this can be turned into a "win" for everyone. So: > Paul/Phoenix-IX -- let the NANOG community know how they/we can help. > > -- > Neil > > On Mon, Nov 16, 2020 at 2:05 PM Kate Gerry <kgerry(a)outlook.com > <mailto:kgerry@outlook.com>> wrote: > > An update on my side, we reached out to PhoenixNAP, one of the > Phoenix-IX's vendors. > > PhoenixNAP reached out all of their contacts at Phoenix-IX and > have received no response. They are in as much of the dark as the > rest of us. I feel like I'm on the Ghost ship Phoenix-IX. > > What I don't understand, is how somebody could abandon a project > without passing it to another person or entity. This is extremely > irresponsible. > > — > Kate > >> On Nov 12, 2020, at 05:11, Marcus Josephson <mjosephson(a)inap.com >> <mailto:mjosephson@inap.com>> wrote: >> >> I tried to get a link to PHX-IX for months. Never heard back from >> them, went with Digital Realty Phoenix >> *From:*NANOG <nanog-bounces+mjosephson=inap.com(a)nanog.org >> <mailto:nanog-bounces+mjosephson=inap.com@nanog.org>>*On Behalf >> Of*Kate Gerry >> *Sent:*Tuesday, November 10, 2020 11:06 AM >> *To:*Matt Hoppes <mattlists(a)rivervalleyinternet.net >> <mailto:mattlists@rivervalleyinternet.net>> >> *Cc:*nanog@nanog.org <mailto:nanog@nanog.org> list >> <nanog(a)nanog.org <mailto:nanog@nanog.org>> >> *Subject:*Re: Phoenix-IX Contact >> Matt, >> I am running on a huge assumption here, but I think Phoenix-IX >> runs on donated infrastructure. From what I recall, there was >> only an NRC to join Phoenix-IX. >> And in regards to Walt's suggestion, it looks like HE already >> started one with Stellar Technologies. https://48ix.net >> <https://48ix.net/> but it is only in a single facility. So until >> that IX grows, both in peers and footprint, I'm stuck on Phoenix-IX. >> I have wondered what happens if a participant storms the IX. Will >> somebody appear? Because attempts to reach their NOC/peering >> handles has resulted in a lack of response. >> I also wonder how the other Ninja-IX exchanges are running, I >> haven't heard anything about them, is there the same lack of >> communication? Or do those have a local staff? >> — >> Kate >> >> >> On Nov 10, 2020, at 06:15, Matt Hoppes >> <mattlists(a)rivervalleyinternet.net >> <mailto:mattlists@rivervalleyinternet.net>> wrote: >> How is the IX still running? Surely someone must be paying >> colo rent? >> >> On 11/10/20 9:03 AM, Eric Kuhnke wrote: >> >> Always a good time for network operators to consider the >> risks of having any one person as a single point of >> failure for something kind of important: >> https://en.wikipedia.org/wiki/Bus_factor >> <https://en.wikipedia.org/wiki/Bus_factor> >> Disaster recovery and continuity of business plans should >> always include the concept of what if some percentage of >> the key team members were to be suddenly unavailable >> permanently (the Malaysian airline incident, for example). >> On Mon, Nov 9, 2020 at 8:08 PM Kate Gerry >> <kgerry(a)outlook.com <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%20%3cmailto:kgerry@outlook.com>>> >> wrote: >> Is there anybody else even there? I thought that it >> was all Paul's show! >> If I was able to (as in, had access to), I would offer >> to help/run >> with the IX. I may live in California, but it's a >> realistic car trip >> back and forth to Phoenix. >> -- >> Kate >> >> On Nov 9, 2020, at 17:58, Mike Hammett >> <nanog(a)ics-il.net >> <mailto:nanog@ics-il.net >> <mailto:nanog@ics-il.net%0b%C2%A0%C2%A0%C2%A0%3cmailto:nanog@ics-il.net>>> >> wrote: >> >> Paul's LinkedIn seems to show that he checked out >> in April. Let me >> know if you have any success reaching anyone there. >> >> >> >> ----- >> Mike Hammett >> Intelligent Computing Solutions >> <http://www.ics-il.com/ <http://www.ics-il.com/>> >> <https://www.facebook.com/ICSIL >> <https://www.facebook.com/ICSIL>><https://plus.google.com/+IntelligentComputingSolutionsDeKalb >> <https://plus.google.com/+IntelligentComputingSolutionsDeKalb>><https://www.linkedin.com/company/intelligent-computing-solutions >> <https://www.linkedin.com/company/intelligent-computing-solutions>><https://twitter.com/ICSIL >> <https://twitter.com/ICSIL>> >> Midwest Internet Exchange >> <http://www.midwest-ix.com/ <http://www.midwest-ix.com/>> >> <https://www.facebook.com/mdwestix >> <https://www.facebook.com/mdwestix>><https://www.linkedin.com/company/midwest-internet-exchange >> <https://www.linkedin.com/company/midwest-internet-exchange>><https://twitter.com/mdwestix >> <https://twitter.com/mdwestix>> >> The Brothers WISP <http://www.thebrotherswisp.com/ >> <http://www.thebrotherswisp.com/>> >> <https://www.facebook.com/thebrotherswisp >> <https://www.facebook.com/thebrotherswisp>><https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg >> <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg>> >> ------------------------------------------------------------------------ >> *From:*"Kate Gerry" <kgerry(a)outlook.com >> <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%20%3cmailto:kgerry@outlook.com>>> >> *To:*"Bill Woodcock" <woody(a)pch.net >> <mailto:woody@pch.net >> <mailto:woody@pch.net%20%3cmailto:woody@pch.net>>> >> *Cc:*nanog@nanog.org <mailto:nanog@nanog.org> >> <mailto:nanog@nanog.org <mailto:nanog@nanog.org>> >> *Sent:*Monday, November 9, 2020 5:44:42 PM >> *Subject:*Re: Phoenix-IX Contact >> >> Just a heads-up, I never heard a word from anybody >> at Phoenix-IX. >> >> Is there anybody still running the IX? Or is it >> just on autopilot? >> It'd be nice if anybody had some information on >> whatever happened >> to Paul. Hopefully he is okay! >> >> -- >> Kate >> >> On Sep 14, 2020, at 13:33, Kate Gerry >> <kgerry(a)outlook.com >> <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%0b%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%3cmailto:kgerry@outlook.com>>> >> wrote: >> >> Thank Bill! I've been trying to reach Paul for >> ages now, >> hopefully he pops back up again. We want to >> upgrade. >> >> On an unrelated note, it looks like somebody >> has their ticket >> system subscribed to the list... Awesome. >> >> *From: *Dating Support >> <dating.support(a)csvwebsupport.com >> <mailto:dating.support@csvwebsupport.com >> <mailto:dating.support@csvwebsupport.com%0b%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%3cmailto:dating.support@csvwebsupport.com>>> >> *Subject: **[#WQV-291-95071]: Phoenix-IX >> Contact* >> *Date: *September 14, 2020 at 12:43:20 PDT >> *To:*kgerry@outlook.com >> <mailto:*kgerry@outlook.com><mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com>> >> *Reply-To:*dating.support@csvwebsupport.com >> <mailto:*dating.support@csvwebsupport.com> >> <mailto:dating.support@csvwebsupport.com >> <mailto:dating.support@csvwebsupport.com>> >> >> Kate Gerry, >> >> Thank you for contacting us. This is an >> automated response >> confirming the receipt of your ticket. Our >> team will get >> back to you within 24 hours. >> >> >> -- >> Kate >> >> >> On Sep 14, 2020, at 12:48, Bill Woodcock >> <woody(a)pch.net >> <mailto:woody@pch.net >> <mailto:woody@pch.net%0b%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%C2%A0%3cmailto:woody@pch.net>>> >> wrote: >> >> >> >> On Sep 14, 2020, at 9:31 PM, Kate Gerry >> <kgerry(a)outlook.com >> <mailto:kgerry@outlook.com >> <mailto:kgerry@outlook.com%20%3cmailto:kgerry@outlook.com>>> >> wrote: >> >> Does anybody have a contact who works >> at Phoenix-IX? I >> have been attempting to reach somebody >> there for a >> while now without any luck. >> >> Attempts to each >> outtopeering(a)phoenix-ix.net >> <mailto:topeering@phoenix-ix.net> >> <mailto:peering@phoenix-ix.net >> <mailto:peering@phoenix-ix.net>>as well as Ninja-IX >> have been without any luck. We also >> tried reaching out >> to Paul Emmons via LinkedIn mail and >> never received a >> response. >> >> >> Paul is the correct person. >> >> -Bill >> >

1 0

ATT Contact for DDoS?
by Sajan Parikh 16 Nov '20

16 Nov '20

Trying to figure out whom to escalate to with ATT to help with a DDoS attack for a network, we are trying to help out. RTBH is not sufficient because they are hitting a large swath of IPs out of the prefixes advertised, and the targets are moving. The network AS itself is the attack target. I'd heard of other operators working with their transit provider's Cybersecurity NOC to filter traffic outside of the US. Does anyone have a good ATT contact for this? Sajan Parikh sajan(a)parikh.io 262.343.5973

1 0

PeeringDB Satisfaction Survey open now til November 20th
by Steve McManus 16 Nov '20

16 Nov '20

PeeringDB is a non-profit, freely available, user-maintained, database of networks, and the go-to location for interconnection data. The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centers, and other interconnection facilities, and is the first stop in making interconnection decisions. We want input from network operators, exchange operators, facility providers, content distributors and anyone who uses our interconnection database. This year we are running an anonymous satisfaction survey in addition to the usual feedback gathering we employ. The survey will be available here: https://surveyhero.com/c/f7be5236 until 23:59 UTC on 20 November 2020. We would like your feedback to help us make PeeringDB more useful to everyone involved in connecting networks.This survey will help us understand what is important to you and how satisfied you are with what we are doing. We will use your responses to focus our product roadmap on the improvements that will make things better for you. If you have specific comments or suggestions, we’d love you to leave them along with your ratings. This is the first survey we are making available in multiple languages. In this survey we are using the six UN languages for the questions. That said, we’re happy with people providing free text comments in another whichever language they are happiest expressing themselves. We’ll share the results and the new product roadmap early in 2021. Steve McManus on behalf of PeeringDB Product Committee

1 1

FCC: Staff Report on T-Mobile Outage on June 15 2020
by Sean Donelan 13 Nov '20

13 Nov '20

FCC Issues Staff Report On T-Mobile Outage https://www.fcc.gov/document/fcc-issues-staff-report-t-mobile-outage-0 The outage was initially caused by an equipment failure and then exacerbated by a network routing misconfiguration that occurred when T-Mobile introduced a new router into its network. In addition, the outage was magnified by a software flaw in T-Mobile’s network that had been latent for months and interfered with customers’ ability to initiate or receive voice calls during the outage. [...] 44. While fiber link failures are common, PSHSB finds that these steps, taken together, will reduce the likelihood that a fiber link failure could result in the recurrence of a similar event in TMobile’s network because traffic would be routed to an alternative path that could handle it. Moreover, if such an event recurred on T-Mobile’s network, it would not cause such a large service disruption because T-Mobile would have improved its networks’ ability to manage congestion in the case of a similar event and would have increased network capacity to maintain the network in a working state even with an increased volume of traffic.

4 4

Weekly Routing Table Report
by cscora＠apnic.net 13 Nov '20

13 Nov '20

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 14 Nov, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 829986 Prefixes after maximum aggregation (per Origin AS): 316702 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 397700 Total ASes present in the Internet Routing Table: 69941 Prefixes per ASN: 11.87 Origin-only ASes present in the Internet Routing Table: 60088 Origin ASes announcing only one prefix: 24866 Transit ASes present in the Internet Routing Table: 9853 Transit-only ASes present in the Internet Routing Table: 299 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 32 Max AS path prepend of ASN ( 45582) 27 Prefixes from unregistered ASNs in the Routing Table: 937 Number of instances of unregistered ASNs: 938 Number of 32-bit ASNs allocated by the RIRs: 34135 Number of 32-bit ASNs visible in the Routing Table: 28269 Prefixes from 32-bit ASNs in the Routing Table: 129495 Number of bogon 32-bit ASNs visible in the Routing Table: 15 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 501 Number of addresses announced to Internet: 2864819456 Equivalent to 170 /8s, 193 /16s and 173 /24s Percentage of available address space announced: 77.4 Percentage of allocated address space announced: 77.4 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 279750 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 217220 Total APNIC prefixes after maximum aggregation: 63608 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 212793 Unique aggregates announced from the APNIC address blocks: 87004 APNIC Region origin ASes present in the Internet Routing Table: 11033 APNIC Prefixes per ASN: 19.29 APNIC Region origin ASes announcing only one prefix: 3122 APNIC Region transit ASes present in the Internet Routing Table: 1612 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 31 Number of APNIC region 32-bit ASNs visible in the Routing Table: 6149 Number of APNIC addresses announced to Internet: 778064768 Equivalent to 46 /8s, 96 /16s and 83 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-143673 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 241972 Total ARIN prefixes after maximum aggregation: 111442 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 239960 Unique aggregates announced from the ARIN address blocks: 114930 ARIN Region origin ASes present in the Internet Routing Table: 18679 ARIN Prefixes per ASN: 12.85 ARIN Region origin ASes announcing only one prefix: 6806 ARIN Region transit ASes present in the Internet Routing Table: 1907 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3544 Number of ARIN addresses announced to Internet: 1093479424 Equivalent to 65 /8s, 45 /16s and 44 /24s ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-401308 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 233793 Total RIPE prefixes after maximum aggregation: 110050 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 229765 Unique aggregates announced from the RIPE address blocks: 137116 RIPE Region origin ASes present in the Internet Routing Table: 27509 RIPE Prefixes per ASN: 8.35 RIPE Region origin ASes announcing only one prefix: 11853 RIPE Region transit ASes present in the Internet Routing Table: 3906 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9652 Number of RIPE addresses announced to Internet: 709605760 Equivalent to 42 /8s, 75 /16s and 185 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-213403 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 111691 Total LACNIC prefixes after maximum aggregation: 26119 LACNIC Deaggregation factor: 4.28 Prefixes being announced from the LACNIC address blocks: 112883 Unique aggregates announced from the LACNIC address blocks: 47965 LACNIC Region origin ASes present in the Internet Routing Table: 10605 LACNIC Prefixes per ASN: 10.64 LACNIC Region origin ASes announcing only one prefix: 2602 LACNIC Region transit ASes present in the Internet Routing Table: 1972 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8193 Number of LACNIC addresses announced to Internet: 174594816 Equivalent to 10 /8s, 104 /16s and 27 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 24371 Total AfriNIC prefixes after maximum aggregation: 4740 AfriNIC Deaggregation factor: 5.14 Prefixes being announced from the AfriNIC address blocks: 34084 Unique aggregates announced from the AfriNIC address blocks: 10272 AfriNIC Region origin ASes present in the Internet Routing Table: 1410 AfriNIC Prefixes per ASN: 24.17 AfriNIC Region origin ASes announcing only one prefix: 482 AfriNIC Region transit ASes present in the Internet Routing Table: 292 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 29 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 731 Number of AfriNIC addresses announced to Internet: 108602624 Equivalent to 6 /8s, 121 /16s and 37 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 45/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7545 5726 778 674 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4738 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3564 1330 21 VIETEL-AS-AP Viettel Group, VN 45899 3259 1896 54 VNPT-AS-VN VNPT Corp, VN 7713 3014 912 562 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2509 9044 57 CMNET-GD Guangdong Mobile Communication 4766 2350 11103 553 KIXS-AS-KR Korea Telecom, KR 9498 2280 450 231 BBIL-AP BHARTI Airtel Ltd., IN 4755 2136 441 190 TATACOMM-AS TATA Communications formerl 9394 2046 4913 16 CTTNET China TieTong Telecommunications Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 11492 4675 310 772 CABLEONE, US 16509 4418 9023 2031 AMAZON-02, US 7155 4035 264 32 VIASAT-SP-BACKBONE, US 22773 3729 2994 198 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3346 1323 82 SHAW, CA 16625 3166 1654 2251 AKAMAI-AS, US 209 2512 5059 512 CENTURYLINK-US-LEGACY-QWEST, US 30036 2476 368 107 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2312 2981 1625 FRONTIER-FRTR, US 20115 2164 2895 506 CHARTER-20115, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6233 1668 143 UNI2-AS, ES 39891 3652 203 21 ALJAWWALSTC-AS, SA 8551 3416 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3270 3347 202 AKAMAI-ASN1, EU 12389 2847 2279 884 ROSTELECOM-AS, RU 47331 2342 407 1755 TTNET, TR 9009 2185 226 1190 M247, GB 34984 2153 352 580 TELLCOM-AS, TR 13188 1611 100 26 TRIOLAN, UA 58224 1364 850 544 TCI, IR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 8145 3441 596 Uninet S.A. de C.V., MX 10620 3405 529 532 Telmex Colombia S.A., CO 11830 2562 369 63 Instituto Costarricense de Electricidad 7303 1478 952 267 Telecom Argentina S.A., AR 6503 1470 312 474 Axtel, S.A.B. de C.V., MX 13999 1467 425 397 Mega Cable, S.A. de C.V., MX 28573 1346 2256 230 CLARO S.A., BR 3816 1163 576 166 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1146 379 39 Telefonica del Peru S.A.A., PE 11664 1006 213 418 Techtel LMDS Comunicaciones Interactiva Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1573 393 22 LINKdotNET-AS, EG 24835 1271 468 27 RAYA-AS, EG 36992 1218 1529 131 ETISALAT-MISR, EG 36903 918 480 94 MT-MPLS, MA 29571 711 68 12 ORANGE-COTE-IVOIRE, CI 6713 552 1863 34 IAM-AS, MA 15399 488 46 16 WANANCHI-, KE 37342 476 32 1 MOVITEL, MZ 36935 446 522 40 Vodafone-, EG 36914 371 82 3 KENET-AS, KE Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 8145 3441 596 Uninet S.A. de C.V., MX 12479 6233 1668 143 UNI2-AS, ES 7545 5726 778 674 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4738 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4675 310 772 CABLEONE, US 16509 4418 9023 2031 AMAZON-02, US 7155 4035 264 32 VIASAT-SP-BACKBONE, US 22773 3729 2994 198 ASN-CXA-ALL-CCI-22773-RDC, US 39891 3652 203 21 ALJAWWALSTC-AS, SA 7552 3564 1330 21 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 6233 6090 UNI2-AS, ES 7545 5726 5052 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4738 4665 ERX-CERNET-BKB China Education and Research Net 7155 4035 4003 VIASAT-SP-BACKBONE, US 11492 4675 3903 CABLEONE, US 39891 3652 3631 ALJAWWALSTC-AS, SA 7552 3564 3543 VIETEL-AS-AP Viettel Group, VN 22773 3729 3531 ASN-CXA-ALL-CCI-22773-RDC, US 8551 3416 3371 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3346 3264 SHAW, CA Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 46766 UNALLOCATED 8.44.208.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US 393489 UNALLOCATED 12.7.109.0/24 7018 ATT-INTERNET4, US 46505 UNALLOCATED 12.7.131.0/24 7018 ATT-INTERNET4, US 15132 UNALLOCATED 12.9.150.0/24 1239 SPRINTLINK, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED Transit: 11426 TWC-11426-CAROLINAS, US 23.142.80.0/24 Origin: 397294 UNASSIGNED Transit: 398559 TUNBROKER, US 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad No. 14, Jala Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:8 /9:13 /10:40 /11:101 /12:292 /13:577 /14:1170 /15:1929 /16:13461 /17:8266 /18:13983 /19:25641 /20:41466 /21:50024 /22:102852 /23:87036 /24:481888 /25:1239 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 5198 6233 UNI2-AS, ES 11492 3798 4675 CABLEONE, US 6327 3143 3346 SHAW, CA 7155 3123 4035 VIASAT-SP-BACKBONE, US 8551 2876 3416 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2856 3729 ASN-CXA-ALL-CCI-22773-RDC, US 8151 2850 8145 Uninet S.A. de C.V., MX 39891 2801 3652 ALJAWWALSTC-AS, SA 30036 2219 2476 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 1995 2312 FRONTIER-FRTR, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1884 2:1207 3:33 4:19 5:3593 6:53 8:1487 9:1 11:1 12:1759 13:343 14:2382 15:72 16:12 17:304 18:91 20:113 23:4020 24:2341 25:3 27:2340 31:2155 32:114 34:1 35:41 36:1067 37:3473 38:1929 39:439 40:150 41:3801 42:626 43:2133 44:227 45:14894 46:3597 47:321 49:1574 50:1671 51:89 52:1127 54:219 55:717 56:6 57:53 58:1792 59:1165 60:815 61:2330 62:2228 63:2008 64:5285 65:2390 66:5111 67:2932 68:1177 69:4090 70:1406 71:684 72:2998 74:2546 75:1462 76:689 77:1989 78:2124 79:2658 80:2039 81:1618 82:1293 83:1071 84:1267 85:2768 86:613 87:1793 88:1432 89:2871 90:386 91:7132 92:1605 93:2531 94:2849 95:3604 96:1240 97:341 98:955 99:979 100:88 101:1025 102:1138 103:24813 104:3606 105:383 106:901 107:2146 108:692 109:3725 110:1984 111:2317 112:1660 113:1514 114:1530 115:1846 116:1851 117:2096 118:2254 119:1789 120:874 121:1023 122:2293 123:2112 124:1617 125:2144 128:1367 129:1241 130:760 131:1924 132:753 133:312 134:1376 135:329 136:670 137:893 138:2318 139:1142 140:766 141:1146 142:989 143:1240 144:1205 145:324 146:1365 147:1226 148:2164 149:1239 150:755 151:1322 152:1572 153:439 154:3310 155:1281 156:2471 157:1120 158:893 159:2003 160:1993 161:1073 162:3184 163:911 164:1514 165:1318 166:592 167:1715 168:3592 169:629 170:4288 171:771 172:2001 173:2936 174:959 175:1062 176:2882 177:4311 178:2764 179:1892 180:2267 181:2556 182:3151 183:1486 184:2431 185:17254 186:3952 187:3078 188:3299 189:2686 190:9113 191:1378 192:10575 193:7794 194:6343 195:4556 196:3148 197:2218 198:6035 199:5917 200:7327 201:5236 202:10552 203:10176 204:4651 205:3077 206:3260 207:3289 208:3997 209:4529 210:4198 211:2080 212:3530 213:3313 214:1194 215:60 216:6146 217:2484 218:853 219:629 220:2037 221:919 222:968 223:1675 End of report

1 0

What's New at NANOG: Latest Interview, Webinars, N80 Spotlight, and more!
by NANOG News 13 Nov '20

13 Nov '20

*“We must always seek to continually learn and better ourselves, and remain humble in the process.” * Cat Gurinsky is hard to miss — even at a crowded NANOG conference. With her vibrant hair, welcoming smile, and a willingness to share her wealth of knowledge, she's the kind of person you immediately notice, and think, "That's someone I definitely want to know." We recently caught up with Cat — Senior Network Engineer at Apple + Vice Chair of the NANOG Program Committee — about her career path as a woman in tech, and how she's paying her own positive experiences forward, via mentorship, teaching, and community service. Read the Feature <https://nanog.org/stories/paying-it-forward/> *Still time to register for today's webinar!* Students + educators: be sure to join us today (11am PST / 2pm EST) for a panel discussion on career opportunities in network engineering, and virtually connect + engage with members of our community from Akamai Technologies, Amazon, Microsoft, and Netflix. Registration is free + open to all. We hope to see you there! Learn More <https://www.nanog.org/meetings/nanog-u-webinars/> *NANOG 80 Spotlight: “Starting a Telephone Company in 2019, or How I Built Fiber to My Neighbors.”* NANOG 80 Virtual may be over, but the hours of archived talks + tutorials, keynotes + panels are just waiting to be explored! First up on our list of must-watch presentations from the conference? Jared Mauch's talk, which details his journey from homeowner to a regulated competitive access provider, while working to provide Internet access to his neighbors. Watch Now <https://nanog.org/news-stories/nanog-tv/nanog-80-webcast/starting-a-telepho…> *Bring your research + ideas to life* Given by many of the industry’s top minds, presentations at NANOG are meant to spark the imagination, encourage dialogue, and drive new solutions to our greatest networking challenges. Interested in sharing your insights at a future NANOG meeting? The NANOG Program Committee accepts proposals on a rolling basis, and would love to see yours! Key Dates: - CFP is OPEN for NANOG 81, 82 and 83 - NANOG 81 presentation slides due: 12/14/2021 - NANOG 81 topics list and highlights posted: 1/11/2021 Learn More <https://www.nanog.org/participate/call-presentations/>

1 0

Fwd: [apnic-talk] APRICOT 2021 PC call for volunteers
by Mark Tinka 12 Nov '20

12 Nov '20

FYI. Mark. -------- Forwarded Message -------- Subject: [apnic-talk] APRICOT 2021 PC call for volunteers Date: Thu, 12 Nov 2020 20:37:10 +1000 From: Philip Smith <pfsinoz(a)gmail.com> Reply-To: APRICOT PC Chairs <pc-chairs(a)apricot.net> Organization: PFS Internet Development Pty Ltd To: apnic-talk(a)lists.apnic.net CC: APRICOT PC Chairs <pc-chairs(a)apricot.net> Hi everyone, As you will no doubt be aware, due to the COVID-19 pandemic, APRICOT 2021 has moved on-line. It will still be hosted, as planned, by PhNOG, the Philippine Network Operator Group. The new format means a reduction in the schedule but retaining the high quality and high relevancy of the content offered over the years. The APRICOT 2021 Programme Committee is responsible for the solicitation and selection of suitable presentation and tutorial content for the APRICOT 2021 conference (https://2021.apricot.net/) The APRICOT PC Chairs are now seeking nominations from the community to join the APRICOT 2021 PC to assist with the development of the programme for APRICOT 2021. Eligible PC candidates are those who have attended APRICOT conferences in the recent past, have broad technical knowledge of Internet operations, and have reasonable familiarity with the format of APRICOT conferences. Having constructive opinions and ideas about how the programme content might be improved is of high value too. PC members are expected to work actively to solicit content and review submissions for technical merit. The PC meets by conference call, weekly in frequency during the three months prior to APRICOT. 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 should include affiliation (if any) and contact details (including e-mail address), and a brief description of why you would make a good addition to the PC. The PC Chairs will accept nominations received by 17:00 UTC+8 on Monday 23rd November 2020, and will announce the new PC shortly thereafter. Many thanks! Mark Tinka, Marijana Novakovic & Philip Smith APRICOT 2021 PC Chairs --

1 0

Passive Wave Primer
by Rod Beck 12 Nov '20

12 Nov '20

Dear Network Gurus, Looking for a tutorial on passive waves. How it works. Pros and cons. . Thanks. Best, Roderick. Roderick Beck VP of Business Development United Cable Company www.unitedcablecompany.com<http://www.unitedcablecompany.com> New York City & Budapest rod.beck(a)unitedcablecompany.com Budapest: 36-70-605-5144 NJ: 908-452-8183 [1467221477350_image005.png]

9 12

plea for comcast/sprint handoff debug help
by Randy Bush 11 Nov '20

11 Nov '20

tl;dr: comcast: does your 50.242.151.5 westin router receive the announcement of 147.28.0.0/20 from sprint's westin router 144.232.9.61? details: 3130 in the westin announces 147.28.0.0/19 and 147.28.0.0/20 to sprint, ntt, and the six and we want to remove the /19 when we stop announcing the /19, a traceroute to comcast through sprint dies at the handoff from sprint to comcast. r0.sea#traceroute 73.47.196.134 source 147.28.7.1 Type escape sequence to abort. Tracing the route to c-73-47-196-134.hsd1.ma.comcast.net (73.47.196.134) VRF info: (vrf in name/id, vrf out name/id) 1 r1.sea.rg.net (147.28.0.5) 0 msec 1 msec 0 msec 2 sl-mpe50-sea-ge-0-0-3-0.sprintlink.net (144.232.9.61) [AS 1239] 1 msec 1 msec 0 msec 3 * * * 4 * * * 5 * * * 6 * * * this would 'normally' (i.e. when the /19 is announced) be r0.sea#traceroute 73.47.196.134 source 147.28.7.1 Type escape sequence to abort. Tracing the route to c-73-47-196-134.hsd1.ma.comcast.net (73.47.196.134) VRF info: (vrf in name/id, vrf out name/id) 1 r1.sea.rg.net (147.28.0.5) 0 msec 1 msec 0 msec 2 sl-mpe50-sea-ge-0-0-3-0.sprintlink.net (144.232.9.61) [AS 1239] 1 msec 0 msec 1 msec 3 be-207-pe02.seattle.wa.ibone.comcast.net (50.242.151.5) [AS 7922] 1 msec 0 msec 0 msec 4 be-10847-cr01.seattle.wa.ibone.comcast.net (68.86.86.225) [AS 7922] 1 msec 1 msec 2 msec etc specifically, when 147.28.0.0/19 is announced, traceroute from 147.28.7.2 through sprint works to comcast. withdraw 147.28.0.0/19, leaving only 147.28.0.0/20, and the traceroute enters sprint but fails at the handoff to comcast. Bad next-hop? not propagated? covid? magic? which is why we wonder what comcast (50.242.151.5) hears from sprint at that handoff note that, at the minute, both the /19 and the /20 are being announced, as we want things to work. so you will not be able to reproduce. so, comcast, are you receiving the announcement of the /20 from sprint? with a good next-hop? randy

8 28