May 2023 - Test - lists.nanog.org

NANOG 88 Keynote, First ABQNOG a Success + Standard Rates Ending Sunday
by Nanog News 25 May '23

25 May '23

*Len Bosack Takes NANOG 88 Keynote Stage* *"From Data Links to Internets: A Quick Tour"* >From concept to equipment needs to various attempts to today—Bosack provides insight into the path of getting from the initial data links before the Internet to the commercial Internet the world has come to know. *REGISTER NOW <https://www.nanog.org/events/nanog-88/agenda/>* *Standard Rates for NANOG 88 Ending Sunday, 28 May* *Register Now for NANOG 88 Virtually or In-Person —12-14, June in Seattle* *REGISTER NOW <https://www.nanog.org/events/nanog-88/registration/registrant>* *First ABQNOG a Success* *“Every NOG Has Left Me with New Info, New Business Contacts, and New Friends”* We caught up with John Osmon, a seasoned industry pro and organizer of ABQNOG to talk about the new regional NOG meeting. *"This event drove home the fact that local events can be highly beneficial. National conferences are one of many ways to open your eyes to what is happening in the industry. It's also important to look around at your neighbors!"* *READ MORE * <https://nanog.org/stories/new-nog-chapter-abqnog-facilitates-successful-fir…> *Join our Whiskey Connoisseurs Affinity Group!* *Find Community in our Online Discussion Threads* The NANOG Affinity Groups are part of the Community Forum and allow our members to connect over shared interests. We need your voice! Connect with others in the tech industry and find mentorship and support while sharing your experiences. *JOIN NOW * <https://community.nanog.org/c/whiskey/42>

1 0

Flowspec Implementation on Cisco ASR
by Pascal Masha 25 May '23

25 May '23

Hi Folks, Has anyone implemented flowspec on Cisco ASR terminating PPPoE users. Flowspec rules should apply to the addresses assigned to PPPoE customers. If yes, kindly share configuration samples.. Regards Paschal Masha

1 0

Seeking recommendations - Network Eng augmentation
by Harry Hoffman 24 May '23

24 May '23

Hi Folks, If you have recommendations on companies that either provide staff augmentation or deliver management services for campus networks would you mind sharing? Cheers, Harry

1 0

Amateur radio @ nanog 88
by Lyndon Nerenberg (VE7TFX/VE6BBM) 23 May '23

23 May '23

For the hams attending 88, should we pick a simplex frequency or two to rendevouz on for beer consumption planning purposes? I'll be armed with a tribander for 146/222/440. --lyndon

1 0

Office 365 Calendar support for macOS Calendar App
by Mark Tinka 23 May '23

23 May '23

Hi all. It may just be me, or it may not, but figured I'd ask... it seems like Microsoft's 365 cloud service does not support the native Calendar app on macOS. Oddly, it works without issue for the native Calendar app in iOS. A bit of Googl'ing and speaking with some 365 customer admins. suggests that "Microsoft do not support Apple products in 365", which sounds most odd to me, as I know a number of Microsoft apps do run on macOS and iOS. Am I off the mark, are others seeing the same, is this a known issue, is it a non-issue? Mark.

3 2

Fw: [Sidrops] Estimating timeline for ASPA Deployment
by Job Snijders 19 May '23

19 May '23

Heya NANOG, I thought this email conversation might be of interest to the group: https://mailarchive.ietf.org/arch/msg/sidrops/RdbccLbXEHUrmmdIS5K9GOdJFXA/ Kind regards, Job ----- Forwarded message from Job Snijders <job(a)fastly.com> ----- Date: Fri, 19 May 2023 20:54:26 +0200 From: Job Snijders <job(a)fastly.com> To: sidrops(a)ietf.org Subject: Re: [Sidrops] Estimating timeline for ASPA Deployment Dear Tony, On Fri, May 19, 2023 at 10:18:58AM -0400, Tony Tauber wrote: > I wonder what people think of likely soonest target dates for adoption > of ASPA? ... Where do psychics go to dance? The crystal ball ;-) ... Disclaimer: The following is based on unsubstantiated information and/or my gutfeeling, I can't vouch for accuracy. I'd like to share some information categorized as 'here work needs to be done', a timeline, and a conclusion referencing earlier RPKI experiences. What needs to happen where? --------------------------- There are a few categories of 'moving parts' in the global Internet routing system that need upgrades in order for ASPA to see widespread adoption. Category | (Non-exhaustive) list of implementations --------------------------+------------------------------------------ Relaying Party packages: OpenBSD rpki-client, NLnet Labs Routinator, LACNIC/NicMX FORT, Cloudflare octorpki, Mikhail Puzanov's rpki-prover, ZDNS RPSTIR2. Signer implementations: NLnet Labs Krill, Dragon Labs rpki.net, and a number of Regional Internet Registries (RIRs) have their own in-house Signer solution. BGP implementations: OpenBSD OpenBGPD, NIC.CZ BIRD, FRRouting, Nokia SR-OS, Cisco IOS XR, Juniper Junos, and many others, see the 'BGP speakers' list at: http://largebgpcommunities.net/implementations/ Standalone RTR servers: StayRTR, NLnet Labs RTRTR, GoRTR, rpkirtr Integrated RTR servers: FORT, Routinator In order for there to be any ASPA deployment, at least one ASPA-capable implementation in all of the RP, Signer, and BGP categories is needed. Without a Signer there isn't anything for the RP to validate, without an RP there isn't any for the BGP speaker to verify BGP UPDATEs against. This is a great example of why the IETF process is so valuable: this process has brought together many stakeholders from different corners of the ecosystem each with different roles to jointly develop a solution for BGP route leaks. Timeline ======== 2023 - "the early wave": ASPA support arrives in select BGP, RP, RTR, and Signer implementations. At the moment of writing OpenBSD rpki-client & OpenBGPD; NLnet Labs Routinator, Krill & RTRTR, StayRTR, rpki-prover, and RIPE NCC have either already released ASPA-capable software or are in an advanced stage to do so. These 'early wave' implementations are incredible achievements as there weren't any examples for the developers to look at, they were building across unchartered territory. One Internet Exchange Point managed to deploy fully ASPA-capable Route Server stack using bleeding edge software, however this effort should be considered an outliner from a timeline perspective: https://mailman.nanog.org/pipermail/nanog/2023-February/221471.html 2024 - The IETF ratifies ASPA by publishing a series of RFC documents detailing the specification. While SIDROPS (this working group) at this moment in time is in the late stages of specifying the ASPA standard, the Internet Engineering Steering Group (IESG) and RFC Editor still need to review the draft documents; all in all this might take another 6-10 months (from now). BGP monitoring software such as BGPAlerter and BGP.Tools might take an interest and start using ASPA data to enhance their alerting capabilities: a growing amount of ASPA data (which can be used to identify route leaks) is becoming available through the 'delegated' (permissionless) RPKI distribution channels. 2025 - Having access to both published RFCs and multiple battle-tested RP implementations (which originated in the 'early wave'), more and more RIRs will feel comfortable scheduling and committing development time to productize an ASPA-offering for their respective RPKI dashboard/web portal/api services. Why 2025? RIRs oftentimes are somewhat conservative and like to see which way the wind blows before offering new services to their constitutes. This is very understandable as for an RIR to offer ASPA the work involved is significantly more than just developing the technical Signer software. RIRs need to design (web-based) user interfaces, which is a big hurdle because for the first time ever RIRs will move away from an 'ROA-centric' user interface to 'the RPKI offers multiple applications' (such as ASPA). As often is the case, going from 0 to 1 is extremely hard, from 1 to 2 still hard, and from 3 onwards it's smoother sailing. RIRs also need time to develop training courses for their internal staff, for external outreach such as capacity building. An RIR can't offer a new feature without explaining to their constitutes what new technology does, how to use it and how to troubleshoot it. It'll take time before RIRs feel comfortable answering questions about ASPA anyone might have. 2026 - General availability in commercial-off-the-shelf BGP speaker implementations (I expect most open-source implementations to be part of the 'early wave' or soon thereafter). Similar to how the RIRs need to develop training and documentation accessible for newcomers to ASPA, the COTS vendors need to develop ASPA-capable software, update procedures in Technical Assistance Centers, update and translate documentation to many languages, train pre-sales engineers. The larger the COTS vendor the more work incorporating a technology like ASPA as part of the product offering is. 2027 - Large nationwide and international ISPs deploy ASPA verification. By now many people will have flown around the world explaining the benefits of ASPA to ISPs both large and small, urging everyone to deploy ASPA verification and drop ASPA-invalid routes. Standing on the shoulders of giants: the published RFCs (by now 3 years old), the early wave RP/RTR implementations, the RIRs supporting ASPA in their hosted offerings since 2025, and now the recently gained access to commercially supported COTS BGP software in hand all contributed towards this moment. The large ISPs can deploy ASPA in their quality assurance environments, assess the revenue impact of deploying "if ASPA-Invalid then drop" EBGP routing policies, and schedule ASPA deployment through the 'once-a-year-sw-upgrade'-window applicable to most of their critical equipment. In conclusion: Of course - come 2027 - many people on social media might be inquiring their ISPs "why haven't you deployed ASPA-verification yet?!?!11" - without realizing that deploying something like ASPA at global scale depends on a complicated long supply chain (complicated both in the technical realm expressed as software, and in the realm of human-to-human conversation such as training and outreach). There are lessons I've learned from the global deployment of RPKI-ROV, a few of which I'd like to share publicly: There was an unfortunate long gap between people being able to create ROAs (without consequence, as for years virtually no organisation was performing RPKI-ROV), and large ISPs truly being able to deploy well-tested stable software to do Route Origin Validation at their EBGP edge; that by the time 2019/2020 rolled around this 'gap' had resulted in many BGP routes being considered ROV-invalid due to (by then inconsequential and forgotten) ROA misconfigurations. This latter aspect in turn made large ISPs extremely hesitant to deploy RPKI-ROV "invalid = drop" EBGP routing policies as a potential for customer outages (aka revenue impact) was perceived. It took building additional software (extensions to traffic analyzers such as pmacct.net and Kentik.com) to be able gauge exactly what the operational and revenue impact of deploying RPKI-ROV would be, before large ISP senior management buy-in happened. Additionally, in the global RPKI-ROV deployment the Internet routing community went from 'zero to one' in context of using *anything* RPKI-based. Much auxiliary infrastructure had to be build indirectly related to the production and consumption of ROAs: for example RIRs had to learn how to operate key materials stored in HSMs, issuance of Root CA certificates, other aspects of PKI. All in all I'm optimistic: with the collective 'first RPKI' experience under our belts, a positive outlook on ASPA-capable open source BGP software suitable for Internet Exchange Point deployments, and a solid diverse set of participants in 'the early wave'; universal deployment of ASPA-verification will be quite the journey - but hopefully smoother because of our prior experiences. この調子でがんばれ！ Job ----- End forwarded message -----

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 19 May '23

19 May '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 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 20 May, 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: 924080 Prefixes after maximum aggregation (per Origin AS): 349822 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 449331 Total ASes present in the Internet Routing Table: 74455 Prefixes per ASN: 12.41 Origin-only ASes present in the Internet Routing Table: 63908 Origin ASes announcing only one prefix: 26264 Transit ASes present in the Internet Routing Table: 10547 Transit-only ASes present in the Internet Routing Table: 432 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: 1074 Number of instances of unregistered ASNs: 1075 Number of 32-bit ASNs allocated by the RIRs: 41898 Number of 32-bit ASNs visible in the Routing Table: 34608 Prefixes from 32-bit ASNs in the Routing Table: 171767 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: 622 Number of addresses announced to Internet: 3057966848 Equivalent to 182 /8s, 68 /16s and 223 /24s Percentage of available address space announced: 82.6 Percentage of allocated address space announced: 82.6 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: 308506 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 245522 Total APNIC prefixes after maximum aggregation: 69449 APNIC Deaggregation factor: 3.54 Prefixes being announced from the APNIC address blocks: 239730 Unique aggregates announced from the APNIC address blocks: 98339 APNIC Region origin ASes present in the Internet Routing Table: 13441 APNIC Prefixes per ASN: 17.84 APNIC Region origin ASes announcing only one prefix: 3959 APNIC Region transit ASes present in the Internet Routing Table: 1799 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8741 Number of APNIC addresses announced to Internet: 773621376 Equivalent to 46 /8s, 28 /16s and 134 /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: 269926 Total ARIN prefixes after maximum aggregation: 122680 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 272754 Unique aggregates announced from the ARIN address blocks: 130386 ARIN Region origin ASes present in the Internet Routing Table: 19115 ARIN Prefixes per ASN: 14.27 ARIN Region origin ASes announcing only one prefix: 6984 ARIN Region transit ASes present in the Internet Routing Table: 1960 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 29 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4800 Number of ARIN addresses announced to Internet: 1281265664 Equivalent to 76 /8s, 94 /16s and 144 /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: 260002 Total RIPE prefixes after maximum aggregation: 122558 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 255899 Unique aggregates announced from the RIPE address blocks: 158414 RIPE Region origin ASes present in the Internet Routing Table: 28333 RIPE Prefixes per ASN: 9.03 RIPE Region origin ASes announcing only one prefix: 12060 RIPE Region transit ASes present in the Internet Routing Table: 3960 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 31 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11194 Number of RIPE addresses announced to Internet: 717968512 Equivalent to 42 /8s, 203 /16s and 84 /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: 118348 Total LACNIC prefixes after maximum aggregation: 28519 LACNIC Deaggregation factor: 4.15 Prefixes being announced from the LACNIC address blocks: 117547 Unique aggregates announced from the LACNIC address blocks: 49414 LACNIC Region origin ASes present in the Internet Routing Table: 11000 LACNIC Prefixes per ASN: 10.69 LACNIC Region origin ASes announcing only one prefix: 2649 LACNIC Region transit ASes present in the Internet Routing Table: 2285 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: 8785 Number of LACNIC addresses announced to Internet: 176955136 Equivalent to 10 /8s, 140 /16s and 31 /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: 29208 Total AfriNIC prefixes after maximum aggregation: 5837 AfriNIC Deaggregation factor: 5.00 Prefixes being announced from the AfriNIC address blocks: 37528 Unique aggregates announced from the AfriNIC address blocks: 12260 AfriNIC Region origin ASes present in the Internet Routing Table: 1743 AfriNIC Prefixes per ASN: 21.53 AfriNIC Region origin ASes announcing only one prefix: 612 AfriNIC Region transit ASes present in the Internet Routing Table: 333 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 40 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1088 Number of AfriNIC addresses announced to Internet: 107748096 Equivalent to 6 /8s, 108 /16s and 27 /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 9500 8706 40 CHINAMOBILE-CN China Mobile Communicati 7545 5718 784 689 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4864 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4131 347 25 FPT-AS-AP FPT Telecom Company, VN 7713 3561 1043 66 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3394 1872 93 VNPT-AS-VN VNPT Corp, VN 7552 3229 1331 21 VIETEL-AS-AP Viettel Group, VN 9498 2961 491 241 BBIL-AP BHARTI Airtel Ltd., IN 4766 2547 11251 591 KIXS-AS-KR Korea Telecom, KR 24560 2399 837 443 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 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 8277 10775 2955 AMAZON-02, US 11492 4537 300 609 CABLEONE, US 7155 4020 281 51 VIASAT-SP-BACKBONE, US 22773 3566 3051 270 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3526 1320 64 SHAW, CA 749 3099 54980 2351 DNIC-AS-00749, US 16625 3099 1559 2343 AKAMAI-AS, US 396982 2656 3592 373 GOOGLE-CLOUD-PLATFORM, US 30036 2500 361 448 MEDIACOM-ENTERPRISE-BUSINESS, US 7018 2495 24148 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 7312 1707 141 UNI2-AS, ES 39891 4765 282 59 ALJAWWALSTC-AS, SA 20940 4105 3399 163 AKAMAI-ASN1, NL 8551 3880 370 37 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2948 2292 910 ROSTELECOM-AS, RU 9009 2700 249 1398 M247, RO 34984 2280 360 609 TELLCOM-AS, TR 6849 2017 307 17 UKRTELNET, UA 58224 1840 948 547 TCI, IR 61317 1610 108 1213 ASDETUK www.heficed.com, US 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 11304 3348 593 Uninet S.A. de C.V., MX 10620 3517 508 854 Telmex Colombia S.A., CO 13999 2346 361 620 Mega Cable, S.A. de C.V., MX 11830 2270 369 64 Instituto Costarricense de Electricidad 28573 1330 2323 240 Claro NXT Telecomunicacoes Ltda, BR 6503 1300 339 514 Axtel, S.A.B. de C.V., MX 3816 1295 766 172 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1134 370 22 Telefonica del Peru S.A.A., PE 11664 1095 180 441 Techtel LMDS Comunicaciones Interactiva 26615 1035 2498 45 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 1605 393 19 LINKdotNET-AS, EG 24835 1496 533 29 RAYA-AS, EG 36992 1338 1518 275 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1028 67 47 ORANGE-COTE-IVOIRE, CI 36935 917 520 42 Vodafone-, EG 6713 550 1861 34 IAM-AS, MA 15399 532 54 48 WANANCHI-, KE 24757 491 73 5 EthioNet-AS, ET 37342 489 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 11304 3348 593 Uninet S.A. de C.V., MX 9808 9500 8706 40 CHINAMOBILE-CN China Mobile Communicati 16509 8277 10775 2955 AMAZON-02, US 12479 7312 1707 141 UNI2-AS, ES 7545 5718 784 689 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4864 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4765 282 59 ALJAWWALSTC-AS, SA 11492 4537 300 609 CABLEONE, US 18403 4131 347 25 FPT-AS-AP FPT Telecom Company, VN 20940 4105 3399 163 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9500 9460 CHINAMOBILE-CN China Mobile Communications Grou 12479 7312 7171 UNI2-AS, ES 16509 8277 5322 AMAZON-02, US 7545 5718 5029 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4864 4789 ERX-CERNET-BKB China Education and Research Net 39891 4765 4706 ALJAWWALSTC-AS, SA 18403 4131 4106 FPT-AS-AP FPT Telecom Company, VN 7155 4020 3969 VIASAT-SP-BACKBONE, US 20940 4105 3942 AKAMAI-ASN1, NL 11492 4537 3928 CABLEONE, US 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 3507 UNALLOCATED 2.57.241.0/24 213035 AS-SERVERION Serverion B.V., 3507 UNALLOCATED 5.105.49.0/24 213035 AS-SERVERION Serverion B.V., 3507 UNALLOCATED 5.105.69.0/24 213035 AS-SERVERION Serverion B.V., 3507 UNALLOCATED 5.105.206.0/24 213035 AS-SERVERION Serverion B.V., 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 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 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.139.232.0/24 Origin: 211619 MAXKO, HR 23.139.232.0/24 Transit: 42864 GIGANET-HU GigaNet Internet Service Prov 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 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 41.57.124.0/22 Origin: 37442 UNASSIGNED 41.57.124.0/22 Transit: 37204 TELONE, ZW 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:39 /11:104 /12:301 /13:581 /14:1200 /15:2053 /16:13479 /17:8235 /18:13852 /19:25136 /20:44172 /21:51371 /22:109824 /23:98240 /24:554716 /25:747 /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 6382 7312 UNI2-AS, ES 8151 5268 11304 Uninet S.A. de C.V., MX 39891 3628 4765 ALJAWWALSTC-AS, SA 11492 3444 4537 CABLEONE, US 8551 3352 3880 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3335 3526 SHAW, CA 7155 3070 4020 VIASAT-SP-BACKBONE, US 22773 2635 3566 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2156 2500 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2070 3517 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:2169 2:1310 3:175 4:5 5:4537 6:130 7:6 8:1553 9:1 11:172 12:1537 13:388 14:2314 15:303 16:188 17:373 18:417 20:258 21:4 22:188 23:6279 24:2606 25:6 27:2463 29:19 31:2492 32:79 34:21 35:112 36:1962 37:4686 38:4636 39:845 40:152 41:3920 42:1962 43:2363 44:310 45:16522 46:4325 47:363 49:1766 50:1859 51:571 52:1600 54:392 55:855 56:8 57:113 58:1890 59:1153 60:987 61:2504 62:2683 63:1927 64:5673 65:2323 66:5033 67:2996 68:1345 69:4109 70:1223 71:670 72:2992 74:2616 75:1557 76:609 77:2449 78:1818 79:3169 80:2122 81:1784 82:1501 83:1276 84:1531 85:2988 86:769 87:2012 88:1171 89:3712 90:618 91:7745 92:2062 93:2619 94:3625 95:4034 96:1308 97:336 98:1152 99:746 100:73 101:1074 102:2689 103:31360 104:4690 105:493 106:952 107:2583 108:1042 109:4415 110:2116 111:3158 112:2037 113:1778 114:1652 115:1979 116:1917 117:2532 118:2616 119:2015 120:1826 121:1130 122:2600 123:2179 124:1610 125:2500 128:1403 129:1026 130:1024 131:1984 132:811 133:422 134:1928 135:305 136:877 137:951 138:2560 139:1565 140:1248 141:1436 142:1458 143:1509 144:1153 145:346 146:1933 147:1586 148:2383 149:2245 150:875 151:1157 152:1826 153:487 154:4404 155:1442 156:1787 157:1317 158:1077 159:2235 160:2540 161:1541 162:3516 163:1526 164:1613 165:1740 166:1076 167:1730 168:3882 169:939 170:4585 171:877 172:3562 173:2958 174:1077 175:1180 176:3716 177:4622 178:3598 179:2212 180:2589 181:3493 182:3392 183:2102 184:2352 185:20272 186:4744 187:4012 188:4120 189:3634 190:9172 191:1444 192:10937 193:8872 194:7308 195:5195 196:3094 197:2378 198:5959 199:6085 200:8055 201:5905 202:10686 203:10304 204:4578 205:3702 206:4292 207:3460 208:4103 209:4901 210:4447 211:2511 212:4174 213:3620 214:1090 215:59 216:6651 217:2697 218:1298 219:578 220:1991 221:976 222:883 223:2183 End of report

1 0

Dominican Republic Landing Station
by Robert DeVita 18 May '23

18 May '23

Does anyone have the address to the Cable Landing Station in Dominican Republic. I am told there is only 1 and I believe its in Punta Cana. Yes I spent 25 minutes trying to google it. Any help would be appreciated Thanks [cid:image001.jpg@01D989BC.76276310] Robert DeVita CEO and Founder t: (469) 581-2160<tel:(469)%20581-2160> | m: (469) 441-8864<tel:(469)%20441-8864> e: radevita(a)mejeticks.com<mailto:radevita@mejeticks.com> | w: mejeticks.com<http://www.example.com/> a: 3100 Carlisle St , Dallas , 75204 [cid:image002.png@01D989BC.76276310]<https://www.linkedin.com/company/mejeticks/> [cid:image003.png@01D989BC.76276310]<https://twitter.com/mejeticks> [cid:image004.png@01D989BC.76276310]<https://www.facebook.com/mejeticks>

2 1

Re: [EXT] Dominican Republic Landing Station
by Thomas E Everett 18 May '23

18 May '23

Puerto plata https://www.fiberatlantic.com/cls/MQDB Thomas E Everett Principal Systems Engineer The MITRE Corp ________________________________ From: NANOG <nanog-bounces+everettt=mitre.org(a)nanog.org> on behalf of Robert DeVita <radevita(a)mejeticks.com> Sent: Thursday, May 18, 2023 8:14:29 PM To: nanog(a)nanog.org <nanog(a)nanog.org> Subject: [EXT] Dominican Republic Landing Station Does anyone have the address to the Cable Landing Station in Dominican Republic. I am told there is only 1 and I believe its in Punta Cana. Yes I spent 25 minutes trying to google it. Any help would be appreciated Thanks [cid:image001.jpg@01D989BC.76276310] Robert DeVita CEO and Founder t: (469) 581-2160<tel:(469)%20581-2160> | m: (469) 441-8864<tel:(469)%20441-8864> e: radevita(a)mejeticks.com<mailto:radevita@mejeticks.com> | w: mejeticks.com<http://www.example.com/> a: 3100 Carlisle St , Dallas , 75204 [cid:image002.png@01D989BC.76276310]<https://www.linkedin.com/company/mejeticks/> [cid:image003.png@01D989BC.76276310]<https://twitter.com/mejeticks> [cid:image004.png@01D989BC.76276310]<https://www.facebook.com/mejeticks>

1 0

Wave out of St Louis to Ashburn
by Louis Alexander 18 May '23

18 May '23

I have been looking for a wave (100g) provider that has a path between St Louis and Ashburn that avoids Dallas, Atlanta and Chicago. i.e. through the middle Struggling to find this on any public network maps. Please respond off list if you're aware of any options here. Regards, Louis

1 0