- Test - lists.nanog.org

New Year, New Sponsorship Opportunities + More
by Nanog News 04 Jan '24

04 Jan '24

*Happy New Year!* *The Best is Yet to Come...* Thank you for joining us for another exciting year at NANOG! Our first meeting of the New Year will kick off Feb. 12 - 14 in Charlotte, NC. Find out more details and register now. *REGISTER NOW * <https://nanog.org/events/nanog-90/register/> *N90 Hotel Venue Confirmed!* *NANOG 90 will Occur at the Le Méridien Charlotte* Registered NANOG attendees, *when logged in with their NANOG profile, *can begin booking now. The room block will be available to all attendees starting Tuesday, 09-January-2024. *BOOK NOW * <https://nanog.org/login/?next=/events/nanog-90/hotel/> *New NANOG 90 Sponsorships Available* *Don't Miss Exciting New Sponsorship Opportunities!* *+ Hotel Keycard Sponsor* *Co-branded hotel key card, available to all NANOG guests registered under the NANOG hotel room block, designed & produced by NANOG.Sign-on deadline Friday Jan 5* *+ Meeting Lanyard Sponsor* *Co-branded meeting badge and lanyard for attendees, designed & produced by NANOG.Sign-on deadline Thursday Jan 11* *+ Meeting T-Shirt Sponsor* *Co-branded meeting t-shirt for attendees, designed & produced by NANOG.Sign-on deadline Friday Jan 19* *Please reach out to Shawn Winstead at swinstead(a)nanog.org <swinstead(a)nanog.org> for more details.* *Video of the Week* *Streaming with Open Caching on the ISP Edge w/ Jeff Budney* Learn about how Verizon has traditionally received streaming traffic, the efforts within industry organizations to improve the streaming video experience through Open Caching and the results seen at Verizon nationwide. *WATCH NOW * <https://www.youtube.com/watch?v=7OAa0s-FDeY>

1 0

Issue with Geolocation in Virginia US
by Raja Sekhar Gullapalli 04 Jan '24

04 Jan '24

Team, We are having issues in our Virginia US office & it shows geolocation in all browsers as Canada instead of US region when we access news.google.com in our PC. Our public ip is 129.46.232.65. This issue is being observed for more than 2 month. Can you help to whom we can contact to resolve the issue. Regards, Raja

8 13

RPKI's 2023 Year in Review - growth, governments, and innovation
by Job Snijders 03 Jan '24

03 Jan '24

Dear all, Happy new year everyone! Having just closed chapter 2023 - let's look back at the previous year. In this memo I'll share some RPKI statistics, summarize highlights from the IETF Standards Development process, and reflect on emerging trends. Year to Year Growth of the distributed RPKI database =============================================================== A straight-forward method to compare to last year is to look at the RPKI's absolute numbers. The below table was constructed by comparing two December 31st RPKIviews.org snapshots [1] of validated RPKI caches, primed with the ARIN, AFRINIC, APNIC, LACNIC, and RIPE NCC Trust Anchors. 2022-12-31 2023-12-31 Total cache size (KiB): 1,240,572 1,546,728 (+25%) Total number of files (objects): 242,969 309,802 (+27%) Publication servers (FQDNs): 52 63 (+21%) Certification authorities: 34,901 40,511 (+16%) Route origin authorizations: 138,323 188,345 (+36%) Unique VRPs: 390,752 497,341 (+27%) IPv4 addresses covered: 1,354,270,410 2,502,293,068 (+85%) IPv6 addresses covered: 9,447 * 10^30 17,263 * 10^30 (+83%) Unique origin ASNs in ROAs: 34,455 40,656 (+18%) The number of IP addresses covered by ROAs almost doubled compared to last year. More than half the ASes in the global Internet routing system are listed as Origin AS in at least one ROA. EOY'23 more unique IPv6 prefix-origin pairs in the DFZ are covered by ROAs than not, with IPv4 likely to follow crossing this threshold in Q1 2024. Kentik [2] estimates that more than half of IP traffic is destined towards ROA covered destinations. APNIC Labs [3] estimates the global "I-Rov Filtering Rate" to be at 22.69% now. These numbers mean it will be worth your while to create and use ROAs for BGP Origin Validation. In short: it's all up and to the right. :-) Increased Government Interest in Internet Routing Security =============================================================== Following the FCC's launch of an inquiry into Internet Routing Vulnerabilities in 2022, in 2023 the agency followed up with a BGP Security Workshop hosted by the Public Safety and Homeland Security Bureau [4], the industry seemed well represented with key players participating. While the USG is still sizing up the industry's posture and contemplating whether regulation is warranted, in the Netherlands the government itself aspires to lead by example: in 2023 the Dutch government committed to use RPKI by the end of 2024 on all new and existing IT systems it operates [5]. Note that this ambition includes both signing ROAs and validating BGP messages! I hope they succeed. Will more governments follow the Dutch lead in 2024? The Rise Of Initiatives Re-evaluating The RPKI Trust Model =============================================================== As the industry saw unprecedented turmoil in the realm of governance of Regional Internet Registries in 2023, two interesting initiatives arose, both aiming to reduce the risk surface associated with blindly trusting 'the RPKI Roots'. In the RPKI hierarchical structure, a Trust Anchor (a root) is an authority for which trust is assumed and not derived. The phrase "assumed trust" means that violation of that trust is out-of-scope for the threat model. On the other hand, the phrase "derived trust" refers to trust automatically and securely computed with subjective logic. In the context of the RPKI, trust is derived according to the rules for validation of RPKI Certificates and Signed Objects. One initiative is to impose 'locally configured constraints' which limit the effective signing authority of an RIR. The other initiative is to instantiate a sixth RPKI trust anchor - which chains up to the existing RIR-operated infrastructure - and impose inter-RIR consensus-driven constraints on that arc. Initiative #1 - operator imposed constraints: Cover letter & discussion: https://mailman.nanog.org/pipermail/nanog/2023-September/223354.html Running code - rpki-client 8.7 & higher https://cdn.openbsd.org/pub/OpenBSD/rpki-client/rpki-client-8.7.txt An internet-draft detailing the implementation: https://datatracker.ietf.org/doc/html/draft-snijders-constraining-rpki-trus… Initiative #2 - externally imposed constraints: Cover letter: https://labs.apnic.net/index.php/2023/12/13/models-of-trust-in-the-rpki/ Running code: https://labs.apnic.net/nro-ta/ A proposal for the validation algorithm to be less rigid & more robust: https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-rpki-validati… I personally don't care much *who* imposes constraints, but at the end of the day - someone's gotta do it. Keep watching this space! SIDROPS - Working Group developments =============================================================== Some quick updates from the IETF working group responsible for development and maintenance of the RPKI technology stack! Running code - now a requirement -------------------------------- The SIDROPS working group set a new rule: Standards Track internet-drafts can only progress towards RFC publication - after - interoperability was demonstrated between at least two independent implementations of the specification: https://mailarchive.ietf.org/arch/msg/sidrops/54iqtt-Ug2lzMbr9KpQOnWsh2JM/ My expectation is that - because of this new rule - we'll see higher quality documents: the proposals more thoroughly tested, increased readability of the internet-draft texts, and less ambiguity in the specifications. Basing Standards Track documents on real implementation experiences (as opposed to gaining real experiences only after publication of as RFC) seems to be the right way to do things. ASPA - where we at? ------------------- In early 2023 a Canadian IXP, YYCIX, became the first to deploy ASPA validation on its IX Route Servers [6] - while this may seem a leap forward towards wider deployment, things are not all said and done. The IETF SIDROPS working group continues to expostulate over things like the ASPA RPKI-To-Router PDU layout. Still, my hope and expectation is that all ASPA-related documents can be finalized in the next few months. I continue to stand by this timeline: https://www.manrs.org/2023/05/estimating-the-timeline-for-aspa-deployment/ Optimizing RSYNC ---------------- RPKI data can be transported in two ways — an HTTPS-based distribution protocol called RRDP, and via RSYNC. Some argue that RSYNC is not the best fit for transport of RPKI files, but unfortunately RRDP isn't without its own issues either. With neither transport protocol being flawless, turns out RSYNC is perfect as a backup option for RRDP! As long as RSYNC is around, we should care for it and continue maintenance & innovation. Rpki-client as validator, and RIPE NCC & APNIC as publishers implemented a mechanism to smoothen switching from RRDP to RSYNC: https://blog.apnic.net/2023/12/04/using-timestamps-inside-rpki-objects-to-o… https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-cms-signing-time My hope is that more validator projects and RIR repositories adopt this mechanism! Final words =============================================================== As more and more networks adopt RPKI, perhaps motivated by government pressure, our collective dependency on RPKI functioning properly and safely increases too. It is awesome to see so many volunteers contribute their valueable time to study, tinker & propose improvements to this wonderful global system. See you next year! - Job Sources: [1]: RPKI Views - http://rpkiviews.org/ http://josephine.sobornost.net/josephine.sobornost.net/rpkidata/2022/12/31/… http://dango.attn.jp/rpkidata/2023/12/31/rpki-20231231T235150Z.tgz [2]: https://www.kentik.com/blog/exploring-the-latest-rpki-rov-adoption-numbers/ [3]: https://stats.labs.apnic.net/rpki [4]: https://www.fcc.gov/news-events/events/2023/07/bgp-security-workshop [5]: https://www.forumstandaardisatie.nl/nieuws/secured-internet-routing-dutch-g… [6]: https://mailman.nanog.org/pipermail/nanog/2023-February/221471.html

1 0

Sufficient Buffer Sizes
by Mike Hammett 03 Jan '24

03 Jan '24

While attempting to ascertain how big of switch buffers I needed in a 100G switch, I rediscovered this article where I first learned about switch buffers. https://fasterdata.es.net/network-tuning/router-switch-buffer-size-issues/#…. It suggests that 60 meg is what you need at 10G. Is that per interface? Would it be linear in that I would need 600 meg at 100G? Some 100G switches I was looking at only had 36 megs, so that's insufficient either way you look at it. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

6 6

Rackspace contact
by Nathan Book 03 Jan '24

03 Jan '24

Can someone at Rackspace contact me off list? We have issues reaching a Rackspace customer's site. Thanks, *Nathan Book* | IT/Broadband Specialist | GMN Broadband

1 0

Hiring: Machine Learning Engineer ICANN Office CTO
by Samaneh Tajalizadehkhoob 02 Jan '24

02 Jan '24

Greetings and happy new year! I lead the Security Stability and Resiliency (SSR) Research team within ICANN’s office of CTO (OCTO). We are now hiring a machine learning engineer who is also familiar with the DNS and routing industry. The position is remote and we rather hire in Europe. But US is an option too. Please take a look and share with whoever would be interested. https://www.linkedin.com/jobs/view/3672913207 Cheers, Samaneh Tajalizadeh Director, Security Stability Resiliency Research ICANN

1 0

Password Reset
by Luiz Rosas 02 Jan '24

02 Jan '24

Hello, I'm trying to reset a password for username "guga0071", but the email address that is attached to this account I no longer have access to. Can you please update my account with the new email address " lrosas0071(a)gmail.com" and provide me with a link to reset my password. Regards Luiz Rosas

5 6

Windstream Contact
by sam 31 Dec '23

31 Dec '23

Dear Nanog I am currently investigating a connection issue we are experiencing with our Midwest office. >From what I can discern and based on the logs I have collected, it appears that the problem lies between Chicago and Lincoln, NE. I am seeking assistance in establishing contact with a Windstream representative. Feel free to send a private message off-list.

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 29 Dec '23

29 Dec '23

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 UKNOF, 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 30 Dec, 2023 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: 939879 Prefixes after maximum aggregation (per Origin AS): 357841 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 456305 Total ASes present in the Internet Routing Table: 75203 Prefixes per ASN: 12.50 Origin-only ASes present in the Internet Routing Table: 64518 Origin ASes announcing only one prefix: 26555 Transit ASes present in the Internet Routing Table: 10685 Transit-only ASes present in the Internet Routing Table: 479 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 121 Max AS path prepend of ASN (150315) 116 Prefixes from unregistered ASNs in the Routing Table: 1054 Number of instances of unregistered ASNs: 1056 Number of 32-bit ASNs allocated by the RIRs: 43280 Number of 32-bit ASNs visible in the Routing Table: 35605 Prefixes from 32-bit ASNs in the Routing Table: 179570 Number of bogon 32-bit ASNs visible in the Routing Table: 19 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 510 Number of addresses announced to Internet: 3046009344 Equivalent to 181 /8s, 142 /16s and 106 /24s Percentage of available address space announced: 82.3 Percentage of allocated address space announced: 82.3 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: 311347 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 251361 Total APNIC prefixes after maximum aggregation: 72465 APNIC Deaggregation factor: 3.47 Prefixes being announced from the APNIC address blocks: 244404 Unique aggregates announced from the APNIC address blocks: 99622 APNIC Region origin ASes present in the Internet Routing Table: 13876 APNIC Prefixes per ASN: 17.61 APNIC Region origin ASes announcing only one prefix: 4178 APNIC Region transit ASes present in the Internet Routing Table: 1870 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 121 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9228 Number of APNIC addresses announced to Internet: 771056768 Equivalent to 45 /8s, 245 /16s and 100 /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-153913 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: 274175 Total ARIN prefixes after maximum aggregation: 124635 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 279162 Unique aggregates announced from the ARIN address blocks: 133085 ARIN Region origin ASes present in the Internet Routing Table: 19081 ARIN Prefixes per ASN: 14.63 ARIN Region origin ASes announcing only one prefix: 6951 ARIN Region transit ASes present in the Internet Routing Table: 1949 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 25 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4826 Number of ARIN addresses announced to Internet: 1273966080 Equivalent to 75 /8s, 239 /16s and 46 /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: 262575 Total RIPE prefixes after maximum aggregation: 125128 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 257040 Unique aggregates announced from the RIPE address blocks: 160933 RIPE Region origin ASes present in the Internet Routing Table: 28502 RIPE Prefixes per ASN: 9.02 RIPE Region origin ASes announcing only one prefix: 12117 RIPE Region transit ASes present in the Internet Routing Table: 3941 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 37 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11494 Number of RIPE addresses announced to Internet: 714558848 Equivalent to 42 /8s, 151 /16s and 77 /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-216475 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: 120300 Total LACNIC prefixes after maximum aggregation: 28858 LACNIC Deaggregation factor: 4.17 Prefixes being announced from the LACNIC address blocks: 118933 Unique aggregates announced from the LACNIC address blocks: 49438 LACNIC Region origin ASes present in the Internet Routing Table: 11053 LACNIC Prefixes per ASN: 10.76 LACNIC Region origin ASes announcing only one prefix: 2666 LACNIC Region transit ASes present in the Internet Routing Table: 2363 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8902 Number of LACNIC addresses announced to Internet: 178379264 Equivalent to 10 /8s, 161 /16s and 218 /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: 30414 Total AfriNIC prefixes after maximum aggregation: 6038 AfriNIC Deaggregation factor: 5.04 Prefixes being announced from the AfriNIC address blocks: 39830 Unique aggregates announced from the AfriNIC address blocks: 12806 AfriNIC Region origin ASes present in the Internet Routing Table: 1815 AfriNIC Prefixes per ASN: 21.94 AfriNIC Region origin ASes announcing only one prefix: 643 AfriNIC Region transit ASes present in the Internet Routing Table: 350 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 27 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1155 Number of AfriNIC addresses announced to Internet: 107755520 Equivalent to 6 /8s, 108 /16s and 56 /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 9808 8739 55 CHINAMOBILE-CN China Mobile Communicati 7545 5675 784 687 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4925 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4536 347 25 FPT-AS-AP FPT Telecom Company, VN 7552 3834 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3598 1043 64 TELKOMNET-AS-AP PT Telekomunikasi Indon 9498 3416 495 254 BBIL-AP BHARTI Airtel Ltd., IN 45899 3269 1872 99 VNPT-AS-VN VNPT Corp, VN 24560 2660 856 371 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 4766 2331 11256 573 KIXS-AS-KR Korea Telecom, KR 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 9451 11199 3359 AMAZON-02, US 11492 4562 303 680 CABLEONE, US 7155 4173 288 96 VIASAT-SP-BACKBONE, US 6327 3567 1320 69 SHAW, CA 22773 3502 3055 299 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3196 1416 2327 AKAMAI-AS, US 749 3162 54930 2414 DNIC-AS-00749, US 367 2969 3840 1418 DNIC-ASBLK-00306-00371, US 396982 2740 3639 386 GOOGLE-CLOUD-PLATFORM, US 7018 2502 23622 1570 ATT-INTERNET4, 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 7564 1714 146 UNI2-AS, ES 39891 4641 279 54 ALJAWWALSTC-AS, SA 20940 4011 3397 142 AKAMAI-ASN1, NL 9009 3487 300 1632 M247, RO 8551 3338 368 34 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 3014 2301 912 ROSTELECOM-AS, RU 34984 2327 359 597 TELLCOM-AS, TR 13188 1607 100 26 TRIOLAN, UA 58224 1510 872 576 TCI, IR 44477 1448 95 714 STARK-INDUSTRIES, GB 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 12153 3384 590 UNINET, MX 10620 3519 497 886 Telmex Colombia S.A., CO 13999 2494 339 636 Mega Cable, S.A. de C.V., MX 11830 2006 369 64 Instituto Costarricense de Electricidad 28573 1345 2318 237 Claro NXT Telecomunicacoes Ltda, BR 3816 1306 787 197 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1245 341 503 Axtel, S.A.B. de C.V., MX 11664 1106 178 423 Techtel LMDS Comunicaciones Interactiva 6147 1087 369 22 Telefonica del Peru S.A.A., PE 22884 1075 116 373 TOTAL PLAY TELECOMUNICACIONES SA DE CV, 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 1588 389 16 LINKdotNET-AS, EG 24835 1548 545 28 RAYA-AS, EG 36992 1360 1518 280 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 29571 1071 69 52 ORANGE-COTE-IVOIRE, CI 36935 936 521 43 Vodafone-, EG 6713 550 1861 34 IAM-AS, MA 15399 533 55 54 WANANCHI-, KE 36914 508 82 3 KENET-AS, KE 37342 481 32 1 MOVITEL, MZ 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 12153 3384 590 UNINET, MX 9808 9808 8739 55 CHINAMOBILE-CN China Mobile Communicati 16509 9451 11199 3359 AMAZON-02, US 12479 7564 1714 146 UNI2-AS, ES 7545 5675 784 687 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4925 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4641 279 54 ALJAWWALSTC-AS, SA 11492 4562 303 680 CABLEONE, US 18403 4536 347 25 FPT-AS-AP FPT Telecom Company, VN 7155 4173 288 96 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9808 9753 CHINAMOBILE-CN China Mobile Communications Grou 12479 7564 7418 UNI2-AS, ES 16509 9451 6092 AMAZON-02, US 7545 5675 4988 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4925 4850 ERX-CERNET-BKB China Education and Research Net 39891 4641 4587 ALJAWWALSTC-AS, SA 18403 4536 4511 FPT-AS-AP FPT Telecom Company, VN 7155 4173 4077 VIASAT-SP-BACKBONE, US 11492 4562 3882 CABLEONE, US 20940 4011 3869 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 65536 DOCUMENT 5.102.30.0/24 65512 -Private Use AS-, ZZ 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 396894 UNALLOCATED 8.28.201.0/24 46887 LIGHTOWER, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, 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.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.176.160.0/24 Origin: 397327 RESERVED, ZZ 23.176.160.0/24 Transit: 19108 SUDDENLINK-COMMUNICATIONS, US 23.189.192.0/24 Origin: 27593 RESERVED, ZZ 23.189.192.0/24 Transit: 174 COGENT-174, US 36.255.139.0/24 Origin: 56050 NEW-SHINE-INTERNET-TH 134 Yenchit Road, 36.255.139.0/24 Transit: 58913 HCL-TH 4819 Supapong 3 Alley, Srinakarin 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:14 /10:37 /11:99 /12:298 /13:581 /14:1193 /15:2062 /16:13443 /17:8271 /18:13804 /19:25155 /20:44412 /21:52007 /22:110959 /23:99840 /24:566972 /25:716 /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 6652 7564 UNI2-AS, ES 8151 6161 12153 UNINET, MX 11492 3476 4562 CABLEONE, US 6327 3371 3567 SHAW, CA 39891 3324 4641 ALJAWWALSTC-AS, SA 7155 3117 4173 VIASAT-SP-BACKBONE, US 8551 2815 3338 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2554 3502 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2130 2473 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2122 3519 Telmex Colombia S.A., CO Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2311 2:1408 3:283 4:5 5:4402 6:163 7:6 8:1533 9:1 11:172 12:1488 13:375 14:2333 15:309 16:206 17:362 18:709 20:344 21:4 22:188 23:6580 24:2606 25:2 27:2554 29:19 31:2547 32:56 34:35 35:121 36:2129 37:4483 38:5819 39:884 40:147 41:4127 42:2203 43:2332 44:325 45:16699 46:4349 47:285 49:1909 50:1887 51:574 52:1593 54:368 55:892 56:5 57:129 58:1926 59:1174 60:1012 61:2568 62:2755 63:1911 64:5501 65:2338 66:5022 67:3040 68:1339 69:4059 70:1180 71:610 72:2921 74:2635 75:1547 76:629 77:2338 78:1827 79:2999 80:2113 81:1875 82:1521 83:1326 84:1631 85:2992 86:793 87:1962 88:1231 89:3966 90:657 91:7904 92:2172 93:2629 94:3590 95:3995 96:1298 97:315 98:1018 99:738 100:94 101:1160 102:3013 103:32524 104:4782 105:601 106:982 107:2764 108:1148 109:4160 110:2141 111:3206 112:2084 113:1782 114:1752 115:1999 116:1983 117:2628 118:2774 119:1944 120:1808 121:1314 122:2646 123:2221 124:1641 125:2811 128:1485 129:919 130:1068 131:1965 132:829 133:411 134:1703 135:304 136:883 137:1036 138:2710 139:1572 140:1342 141:1340 142:1540 143:1532 144:1002 145:340 146:2015 147:1634 148:2485 149:2398 150:1015 151:1311 152:1848 153:529 154:5498 155:1369 156:2108 157:1369 158:1079 159:2209 160:2622 161:1616 162:3597 163:1673 164:1631 165:2099 166:1076 167:1740 168:3848 169:792 170:4698 171:996 172:3775 173:3019 174:896 175:1217 176:3598 177:4719 178:3534 179:2234 180:2355 181:3644 182:3455 183:2025 184:2273 185:20509 186:4807 187:4379 188:4019 189:3964 190:9338 191:1502 192:11033 193:8983 194:7360 195:5236 196:3134 197:2609 198:6020 199:6841 200:8096 201:6251 202:10563 203:10105 204:4589 205:3676 206:4510 207:3500 208:4101 209:4955 210:4625 211:2589 212:4218 213:3390 214:1113 215:50 216:6781 217:2773 218:1336 219:588 220:2051 221:1021 222:870 223:2227 End of report

1 0

NANOG 90 Venue Update
by NANOG Support 28 Dec '23

28 Dec '23

Dear NANOG Community, This letter is an update on the upcoming NANOG 90, February 2024 conference. As we announced at NANOG 89, due to unforeseen circumstances, our contracted meeting venue canceled our contract and it became necessary for us to change the venue and date for the upcoming NANOG 90 meeting (12-14 February 2024). This has resulted in the delay in posting the hotel guest room information as we work to negotiate an agreement with a new property. The delay has been due to the hotel network infrastructure, which is not at the level NANOG requires to support its network needs. We are happy to report at this time a solution has been developed, and contract signing is underway. Once the contract is completed, there will be a room block we will publish for registered NANOG conference attendees to begin booking rooms. The room block will be available to all one week later. We appreciate your patience as we worked through this process, along with your unflagging support of NANOG. Sincerely, Darrieux Harvey NANOG Director of Meetings + Interim Operations Director

2 1