- NANOG - lists.nanog.org

WATCH NOW | NANOG 86 Talks, NANOG U + "Internet Innovators"
by Nanog News 03 Nov '22

03 Nov '22

*NANOG 86 Talks are LIVE! * Have you subscribed to our Youtube channel? Subscribe now <https://www.youtube.com/channel/UCIvcN8QNgRGNW9osYLGsjQQ> and be the first to know when new videos are uploaded. The full webcast is available in the "NANOG 86" playlist. *WATCH NOW * <https://www.youtube.com/playlist?list=PLO8DR5ZGla8jtquZaIDizi3q-GnoUgrQQ> *VIDEO: NANOG U Provides Incredible Opportunities for NexGen Tech* *City of Montgomery hosted the two-day event * >From networking opportunities with top-tier tech reps to educational info + career tips from industry leaders — NANOG U is the ultimate foot in the door for anyone interested in pursuing the technical field! Recently, the City of Montgomery hosted our two-day NANOG U Fall 2022 Tour. ARIN, ICANN, Amazon Web Services, Microsoft, + more were in attendance. *WATCH NOW * <https://www.nanog.org/news-stories/nanog-tv/nanog-u/nanog-u-fall-2022-tour-…> *New Episode of "Internet Innovators"* *"Father of the African Internet" Nii Quaynor talks to NANOG* If you watch "Internet Innovators" in Africa, you have Nii Quaynor to thank. Quaynor has pioneered internet development and expansion throughout Africa and is responsible for the first Internet connectivity throughout the continent. *WATCH NOW to learn:* - His story - The current status of the Internet in Africa (post-pandemic) - "Building the Blockchain" + why he thinks Africa should be a cashless society - How to introduce innovation to a new culture - His next five years - + More *WATCH NOW * <https://www.nanog.org/news-stories/nanog-tv/internet-innovators/internet-in…> *2022 NANOG Elections Results* The 2022 NANOG election results are in! Board of Directors Candidates Proposed Bylaw Changes Key Dates Election Results For a full overview and final results click below. *VIEW NOW * <https://www.nanog.org/members/elections/past-elections/2022-nanog-elections…>

1 0

DNS OARC 40 - Call for Contribitions
by John Todd 03 Nov '22

03 Nov '22

OARC 40 will be a two-day hybrid meeting held on 16 & 17 February in Atlanta (GA), USA at 10:00 AM (Local time - EST (UTC-05:00)). The onsite part of the meeting will be colocated with NANOG 87. The Programme Committee is seeking contributions from the community. All DNS-related subjects and suggestions for discussion topics are welcome. For inspiration, we provide a non-exhaustive list of ideas: - Operations: Any operational gotchas, lessons learned from an outage, details/reasons for a recent outage (how to improve TTR, tooling). - Deployment: DNS config management and release process. - Monitoring: Log ingestion pipeline, analytics infrastructure, anomaly detection. - Scaling: DNS performance management and metrics. Increasing DNS Server Efficiency - Security/Privacy: DNSSEC signing and validation, key storage, rollovers, qname minimization, DoH/DoT The presentations can be either a full-length presentation - 20 mins (+5 mins Q/A) or a lightning presentation - 10 mins (+5 mins for Q/A) Workshop Milestones: 2022-10-22 Submissions open via Indico 2022-12-20 Deadline for submission (23:59 UTC) 2023-01-10 Preliminary list of contributions published 2023-01-17 Full agenda published 2023-01-30 Deadline for slideset submission and Rehearsal 2023-02-16 OARC 40 Workshop - Day1 2023-02-17 OARC 40 Workshop - Day2 The Registration page and details for presentation submission are published at: <https://www.dns-oarc.net/oarc40> To allow the Programme Committee to make objective assessments of submissions, so as to ensure the quality of the workshop, submissions SHOULD include slides. Draft > slides are acceptable on submission. Guidelines for presentation > slides: https://www.grammarly.com/blog/presentation-tips/ Additional information for speakers of OARC 40 - Your talk will be broadcast live and recorded for future reference - Your presentation slides will be available for delegates and others to download and refer to, before, during and after the meeting - Remote speakers have mandatory rehearsal on 2023-01-31 at 14:00 UTC. It would be very useful to have your slides (even if draft) ready for this. Note: DNS-OARC provides registration fee waivers for the workshop to support those who are part of underrepresented groups to speak at and/or attend DNS-OARC. More details will be provided when registration opens. If you have questions or concerns you can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via submissions(a)dns-oarc.net John Todd, for the DNS-OARC Programme Committee OARC depends on sponsorship to fund its workshops and associated social events. Please contact sponsor(a)dns-oarc.net if your organization is interested in becoming a sponsor. (Please note that OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.) -- John Todd - jtodd(a)quad9.net General Manager - Quad9 Recursive Resolver

1 0

Understanding impact of RPKI and ROA on existing advertisements
by Samuel Jackson 02 Nov '22

02 Nov '22

Hello, I am new to RPKI/ROA and still learning about RPKI. From all my reading on ARIN's documents I am not able to answer some of my questions. We have a public ARIN block and advertise smaller subnets from that to our ISP's. We do not have any RPKI configs. We need to setup ROA's to take another subnet from the ARIN block to AWS. Reading ARIN's docs, it seems I need to get setup on their Hosted RPKI service after which I can configure ROA's for the networks I am taking to AWS. My question is, will this impact my existing advertisements to my ISP's. The current advertisements do not have ROA's. Will having RPKI for my ARIN network, without ROA's for the existing advertisements impact me? Thanks for your help. Ref: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-byoip.html https://www.arin.net/resources/manage/rpki/roa_request/ https://www.arin.net/resources/manage/rpki/hosted/

10 12

ARIN RPA updated (again) to address TAL distribution (Re: ARIN RPKI services terms/conditions - Change to Management of the Trust Anchor Locator for ARIN’s RPKI Service)
by Christopher S. Yoo 02 Nov '22

02 Nov '22

As the coauthors of the 2019 NSF-supported report that contributed to the current momentum toward overcoming the barriers RPKI adoption, a prior posting asked for our assessment of the changes. Our apologies that we won't be able to join you at this NANOG. We hope to put together some type of program in Atlanta in February. We would say that intent of ARIN's Sept. 26 and 29 updates ((link<https://www.arin.net/announcements/2022/documents/rpa_092622_redline.pdf> and link<https://www.arin.net/announcements/2022/documents/rpa_092922_redline.pdf>) to the RPA-to permit distribution of the TAL without signing the RPA-represent positive steps to address the most significant concern that we raised. In particular, the language in Section 5 added by the Sept. 29 update explicitly stating, "Notwithstanding the foregoing, You are specifically allowed to publicly distribute the ARIN TAL, including by embedding the ARIN TAL in relying party software," appears to authorize including ARIN's TAL in all distributions of validator software, and RPKI adopters would no longer need to download ARIN's TAL from its website. If effective, this is would remove the single most important legal obstacle to broader use of RPKI. The continuing wrinkle is that Section 5 authorizes distribution of ORCP services (including the ARIN TAL) only as permitted by the ORCP service terms. Section 9 requires third parties receiving this information either to have agreed to the RPA or to have entered into an agreement with the distributing party that includes the key terms of the RPA. That would suggest that anyone distributing validator software with ARIN's TAL must ensure that the recipient has agreed to the RPA in order to avoid violating the ORCP service terms. Although open source typically relies on licenses that are good against all users regardless of knowledge or assent (because they sound in property instead of contract), assent to the terms of the RPA could be incorporated into the distribution process, perhaps in the same manner used for other certificate authorities, which typically have terms of use. Another comment on this thread asked if ARIN has now addressed the other issues raised by our report. It is our assessment that ARIN has adequately addressed three of our other concerns, has announced its intention to address two others, and partially addressed one. The three issues that ARIN has adequately addressed include: * Dropping provision of the RSA requiring legacy address holders to acknowledge ARIN's property rights in IP addresses: dropped in update to LRSA dated Sept. 12, 2022 (link<https://www.arin.net/about/corporate/agreements/rsav13_changes.pdf>). * Drop provision of RPA prohibiting sharing of RPKI-derived data in a machine-readable format: authorized for informational purposes by update to RPA dated Oct. 21, 2019 (link<https://www.arin.net/vault/announcements/2019/20191021.html>); authorized for routing purposes by update to RPA dated Sept. 26, 2022 (link<https://www.arin.net/announcements/2022/documents/rpa_092622_redline.pdf>). * Better dissemination of best practices to the community: addressed by expansion of RPKI training at FISPA, WISPA, CaribNOG, and NANOG. ARIN has its intention to address two of our other concerns in the near future: * Better disclosure to government agencies of ARIN's willingness to waive insemination and choice of law clauses when barred by law: likely to be addressed by ARIN's announced plans to create webpage specifically for governments. * Better disclosure of operational practices, such as uptime, update frequency, and response expectations: likely to be addressed further by planned update to certificate practices statement. It partially addressed one concern that we raised. * Dropping blanket indemnification clause in favor of disclaimer of warranties and liability: revised RPA to exclude indemnification for ARIN's gross negligence by update to RPA dated Oct. 21, 2019 (link<https://www.arin.net/vault/announcements/2019/20191021.html>). We hope these comments are helpful and look forward to continuing to work with the community on removing the remaining legal barriers to RPKI adoption. Christopher Yoo (on behalf of myself and David Wishnick)

2 2

Equinix: Still looking for routeserver community info
by Elmar K. Bins 02 Nov '22

02 Nov '22

Hi folks, my inquiry kind of dead-ended here; I still have trouble in Warsaw (could be the name of a movie). Whether I send my prefix with NO_EXPORT, or with the secretly documented 24115:65281 (or 2 or 3) (from https://ix.equinix.com/portal/resources/mlpe-information) the routeserver just eats my prefix and doesn't forward... Does anybody have experience with getting the MLPE system to do what would be required (i.e., take the prefix, attach a NO_EXPORT, and forward)? Thanks! Elmar. PS: Anybody from Equinix wanting to shed some light on this, please...

1 0

Anyone from Verisign peering lurking?
by Bryan Holloway 02 Nov '22

02 Nov '22

Trying to resolve a peering issue; e-mails to listed contacts have been fruitless ... thanks!

1 0

NOTICE - Change in access to ARIN Online (was: Fwd: [arin-announce] ARIN to Enforce 2FA on all ARIN Online Accounts Starting 1 February 2023)
by John Curran 01 Nov '22

01 Nov '22

NANOGers - Important information - please note this change will affect how access to your ARIN Online account and related administration of your number resources. FYI, /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [arin-announce] ARIN to Enforce 2FA on all ARIN Online Accounts Starting 1 February 2023 Date: 1 November 2022 at 10:10:10 AM EDT To: "arin-announce(a)arin.net<mailto:arin-announce@arin.net>" <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> Beginning 1 February 2023, ARIN will require Two-Factor Authentication (2FA) on all ARIN Online accounts. Customers will be able to choose between Time-Based One-Time password (TOTP), SMS-based, and Fast Identity Online 2 (FIDO2). We had initially planned to enforce 2FA following the deployment of SMS-based 2FA, but we opted to delay the implementation of enforcing 2FA for all ARIN Online accounts until we were able to complete implementation of FIDO2 due to significant community feedback received during our community consultation (https://www.arin.net/announcements/20220524-consultopen/) on this change. FIDO2 support is pending release on 19 December 2022. You can learn more about your 2FA options by visiting our website: https://www.arin.net/reference/materials/security/twofactor/ By requiring 2FA for ARIN Online accounts that control number resources, the ARIN community should see stronger security for the registry, reduced risk of account fraud attempts, and increased confidence in the integrity of their ARIN resources. We strongly encourage account holders to set up 2FA in advance of the flag day for enforcement so that this change is not interruptive to your account access after 1 February 2023. Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN) HELPFUL RESOURCES: Need help setting up your two-factor authentication? Visit https://www.arin.net/2fa to get started. You’ll find guides on enabling 2FA via an authenticator application such as Google Authenticator, SMS or Voice, and (coming soon) FIDO2. We also provide information on how to receive and save your 2FA recovery codes, as well as what to do if you’ve lost access to your authenticator or SMS/Voice phone number.

1 0

network configuration survey
by 徐惠三 01 Nov '22

01 Nov '22

Dear network operators, I hope this email finds you well. I am a first-year graduate student and I have been working on a survey for network configuration intent.I will be much appreciated if you could spare some time to answer my following questions. 1.For BGP communities, I have referred to BGP Community Guides | One Step for some communities opened by ISPs. I wonder if the ISPs will open all their communities and logics, or there are still more kept secret. If there are some secret community values and control logics, how can I make sure the community appended within my AS will not coincide with the ISPs' route maps and yield unexpected results? Have you ever observed similar errors? 2.Another question is about trouble-shooting. Suppose you find some errors in local AS (e.g cannot reach certain destination), yet you only have access to local RIBs or configurations. How do you try to fix it with these information? Is it necessary to refer to other ASes' information? If yes, which ASes are selected and how do you communicate with them? 3.Finally, I also want to know what are some of the properties to be expected if a tool is to be designed for the circumstance in question 2. Should it be privacy-preserving or scalable? What size of network is it expected to work on? And what is the expected processing time of the tool for different sizes of networks? You can fill in your answers at: https://docs.google.com/forms/d/e/1FAIpQLScQJIfQARRdZvk5Wmb5-sHvb02uZdE1NgZ… Thank you very much and I'm looking forward to hearing from you. Best regards, Huisan Xu

1 0

itojun
by Randy Bush 28 Oct '22

28 Oct '22

and the third giant to have died in october, itojun hagino died on this day in 2007. ipv6 owes a great debt to itojun; as do a bunch of other technoogies and many people. a wise and gentle soul. i dread october. randy http://www.itojun.org/itojun.html http://www.itojun.org/personal.html https://asiajin.com/blog/2007/10/jun-ichiro-itojun-hagino-dies-at-37-ipv6-d…

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 28 Oct '22

28 Oct '22

This is an automated weekly mailing describing the state of the Global IPv4 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 29 Oct, 2022 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 913431 Prefixes after maximum aggregation (per Origin AS): 344677 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 440775 Total ASes present in the Internet Routing Table: 73756 Prefixes per ASN: 12.38 Origin-only ASes present in the Internet Routing Table: 63346 Origin ASes announcing only one prefix: 26009 Transit ASes present in the Internet Routing Table: 10410 Transit-only ASes present in the Internet Routing Table: 411 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1068 Number of instances of unregistered ASNs: 1071 Number of 32-bit ASNs allocated by the RIRs: 40510 Number of 32-bit ASNs visible in the Routing Table: 33589 Prefixes from 32-bit ASNs in the Routing Table: 162188 Number of bogon 32-bit ASNs visible in the Routing Table: 14 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 527 Number of addresses announced to Internet: 3064049024 Equivalent to 182 /8s, 161 /16s and 173 /24s Percentage of available address space announced: 82.8 Percentage of allocated address space announced: 82.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 310290 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 238504 Total APNIC prefixes after maximum aggregation: 67891 APNIC Deaggregation factor: 3.51 Prefixes being announced from the APNIC address blocks: 233487 Unique aggregates announced from the APNIC address blocks: 96685 APNIC Region origin ASes present in the Internet Routing Table: 13050 APNIC Prefixes per ASN: 17.89 APNIC Region origin ASes announcing only one prefix: 3749 APNIC Region transit ASes present in the Internet Routing Table: 1763 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 33 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8296 Number of APNIC addresses announced to Internet: 773644800 Equivalent to 46 /8s, 28 /16s and 226 /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-151865 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: 266822 Total ARIN prefixes after maximum aggregation: 121568 ARIN Deaggregation factor: 2.19 Prefixes being announced from the ARIN address blocks: 268075 Unique aggregates announced from the ARIN address blocks: 128894 ARIN Region origin ASes present in the Internet Routing Table: 19061 ARIN Prefixes per ASN: 14.06 ARIN Region origin ASes announcing only one prefix: 6959 ARIN Region transit ASes present in the Internet Routing Table: 1924 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4661 Number of ARIN addresses announced to Internet: 1289996800 Equivalent to 76 /8s, 227 /16s and 202 /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: 261940 Total RIPE prefixes after maximum aggregation: 120746 RIPE Deaggregation factor: 2.17 Prefixes being announced from the RIPE address blocks: 258812 Unique aggregates announced from the RIPE address blocks: 154488 RIPE Region origin ASes present in the Internet Routing Table: 28152 RIPE Prefixes per ASN: 9.19 RIPE Region origin ASes announcing only one prefix: 11998 RIPE Region transit ASes present in the Internet Routing Table: 3966 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10864 Number of RIPE addresses announced to Internet: 716309888 Equivalent to 42 /8s, 178 /16s and 5 /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: 116612 Total LACNIC prefixes after maximum aggregation: 28105 LACNIC Deaggregation factor: 4.15 Prefixes being announced from the LACNIC address blocks: 116120 Unique aggregates announced from the LACNIC address blocks: 48367 LACNIC Region origin ASes present in the Internet Routing Table: 10985 LACNIC Prefixes per ASN: 10.57 LACNIC Region origin ASes announcing only one prefix: 2707 LACNIC Region transit ASes present in the Internet Routing Table: 2246 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8744 Number of LACNIC addresses announced to Internet: 175875840 Equivalent to 10 /8s, 123 /16s and 167 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 28485 Total AfriNIC prefixes after maximum aggregation: 5578 AfriNIC Deaggregation factor: 5.11 Prefixes being announced from the AfriNIC address blocks: 36410 Unique aggregates announced from the AfriNIC address blocks: 11915 AfriNIC Region origin ASes present in the Internet Routing Table: 1698 AfriNIC Prefixes per ASN: 21.44 AfriNIC Region origin ASes announcing only one prefix: 596 AfriNIC Region transit ASes present in the Internet Routing Table: 326 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1024 Number of AfriNIC addresses announced to Internet: 107920128 Equivalent to 6 /8s, 110 /16s and 187 /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 9808 9074 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5937 786 695 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4726 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3614 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3500 1042 61 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3390 1877 66 VNPT-AS-VN VNPT Corp, VN 4766 2533 11252 600 KIXS-AS-KR Korea Telecom, KR 9498 2491 499 237 BBIL-AP BHARTI Airtel Ltd., IN 24560 2243 851 409 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2179 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 7449 10588 2892 AMAZON-02, US 11492 4631 306 502 CABLEONE, US 7155 3898 265 32 VIASAT-SP-BACKBONE, US 22773 3733 3057 322 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3533 1843 2542 AKAMAI-AS, US 6327 3516 1320 63 SHAW, CA 749 3029 50727 2287 DNIC-AS-00749, US 7018 2612 24153 1578 ATT-INTERNET4, US 30036 2606 372 243 MEDIACOM-ENTERPRISE-BUSINESS, US 396982 2558 3480 349 GOOGLE-CLOUD-PLATFORM, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6919 1730 144 UNI2-AS, ES 9121 6835 1692 17 TTNET, TR 20940 4108 3400 182 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA 8551 3980 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2950 2290 913 ROSTELECOM-AS, RU 9009 2625 252 1348 M247, RO 6849 2439 339 20 UKRTELNET, UA 34984 2240 357 614 TELLCOM-AS, TR 47331 2077 322 1580 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10856 3298 605 Uninet S.A. de C.V., MX 10620 3471 510 838 Telmex Colombia S.A., CO 11830 2295 369 64 Instituto Costarricense de Electricidad 13999 2091 341 548 Mega Cable, S.A. de C.V., MX 28573 1334 2328 263 Claro NXT Telecomunicacoes Ltda, BR 6503 1295 338 521 Axtel, S.A.B. de C.V., MX 3816 1285 722 152 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 1090 181 467 Techtel LMDS Comunicaciones Interactiva 6147 1087 369 22 Telefonica del Peru S.A.A., PE 26615 989 2466 43 TIM SA, BR Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1575 393 21 LINKdotNET-AS, EG 24835 1545 521 31 RAYA-AS, EG 36992 1350 1519 270 ETISALAT-MISR, EG 36903 1248 550 99 MT-MPLS, MA 29571 992 68 32 ORANGE-COTE-IVOIRE, CI 36935 815 520 42 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 526 53 42 WANANCHI-, KE 37342 495 32 1 MOVITEL, MZ 23889 400 231 14 MauritiusTelecom, MU Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10856 3298 605 Uninet S.A. de C.V., MX 9808 9074 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7449 10588 2892 AMAZON-02, US 12479 6919 1730 144 UNI2-AS, ES 9121 6835 1692 17 TTNET, TR 7545 5937 786 695 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4726 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4631 306 502 CABLEONE, US 20940 4108 3400 182 AKAMAI-ASN1, NL 39891 4010 234 47 ALJAWWALSTC-AS, SA Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9074 9024 CHINAMOBILE-CN China Mobile Communications Grou 9121 6835 6818 TTNET, TR 12479 6919 6775 UNI2-AS, ES 7545 5937 5242 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4726 4651 ERX-CERNET-BKB China Education and Research Net 16509 7449 4557 AMAZON-02, US 11492 4631 4129 CABLEONE, US 39891 4010 3963 ALJAWWALSTC-AS, SA 8551 3980 3942 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 20940 4108 3926 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 16641 UNALLOCATED 8.10.194.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.10.210.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.12.250.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.14.115.0/24 3356 LEVEL3, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 25674 UNALLOCATED 8.19.146.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.136.112.0/24 Origin: 54835 UNASSIGNED 23.136.112.0/24 Transit: 21559 OSNET, PR 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.158.240.0/24 Origin: 13465 UNASSIGNED 23.158.240.0/24 Transit: 33185 HIVE-DATA-CENTER, CA 23.181.240.0/24 Origin: 399613 UNASSIGNED 23.181.240.0/24 Transit: 11992 CENTENNIAL-, PR 24.48.128.0/19 Origin: 29866 OPTICALTEL, US 24.48.128.0/19 Transit: 3257 GTT-BACKBONE GTT, US Complete listing at https://thyme.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:16 /9:13 /10:39 /11:100 /12:294 /13:589 /14:1202 /15:2045 /16:13495 /17:8343 /18:13975 /19:25200 /20:44384 /21:52211 /22:109833 /23:97775 /24:543132 /25:785 /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 9121 5981 6835 TTNET, TR 12479 5926 6919 UNI2-AS, ES 8151 4819 10856 Uninet S.A. de C.V., MX 11492 3537 4631 CABLEONE, US 8551 3444 3980 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3324 3516 SHAW, CA 39891 3193 4010 ALJAWWALSTC-AS, SA 7155 2988 3898 VIASAT-SP-BACKBONE, US 22773 2767 3733 ASN-CXA-ALL-CCI-22773-RDC, US 6849 2302 2439 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1905 2:1015 3:167 4:5 5:3998 6:116 7:5 8:1598 9:1 11:173 12:1621 13:354 14:2341 15:277 16:69 17:359 18:346 20:241 21:4 22:188 23:5980 24:2466 25:6 27:2710 29:19 31:2453 32:94 34:7 35:92 36:1799 37:4498 38:3742 39:753 40:159 41:3908 42:1180 43:2300 44:297 45:16294 46:4208 47:375 49:1724 50:1931 51:244 52:1500 54:398 55:843 56:8 57:78 58:1790 59:1164 60:996 61:2404 62:2583 63:1968 64:5628 65:2328 66:4853 67:2980 68:1379 69:4157 70:1300 71:679 72:2971 74:2652 75:1473 76:600 77:2251 78:3964 79:3146 80:2041 81:1823 82:1521 83:1218 84:1438 85:3734 86:731 87:1918 88:2843 89:3423 90:549 91:7595 92:2068 93:2549 94:3546 95:4822 96:1353 97:346 98:1169 99:739 100:69 101:1068 102:2336 103:30323 104:4519 105:477 106:890 107:2539 108:905 109:4324 110:2003 111:3323 112:2050 113:1551 114:1520 115:2023 116:1922 117:2475 118:2321 119:1849 120:1731 121:1090 122:2565 123:2117 124:1553 125:2183 128:1262 129:986 130:975 131:2015 132:846 133:379 134:1889 135:290 136:876 137:900 138:2496 139:1515 140:1127 141:1467 142:1402 143:1402 144:1203 145:353 146:1872 147:1536 148:2260 149:1830 150:875 151:1135 152:1824 153:469 154:3821 155:1428 156:1638 157:1302 158:1045 159:2206 160:2562 161:1383 162:3503 163:1433 164:1684 165:1637 166:809 167:1718 168:3815 169:903 170:4536 171:851 172:3463 173:3109 174:1041 175:1155 176:3595 177:4760 178:3528 179:2121 180:2341 181:3319 182:3238 183:1942 184:2356 185:19846 186:4531 187:3951 188:4047 189:3473 190:8984 191:1432 192:10987 193:8755 194:7175 195:5089 196:2976 197:2473 198:6008 199:6067 200:7605 201:5818 202:10544 203:10038 204:4601 205:3497 206:3902 207:3420 208:4092 209:4800 210:4336 211:2437 212:4055 213:3577 214:1082 215:53 216:6486 217:2624 218:1292 219:576 220:2045 221:924 222:827 223:2014 End of report

1 0