February 2026 - NANOG - lists.nanog.org

META. Performance degradation caused by uRPF or bundle issues within Meta network
by Alejandro 23 Feb '26

23 Feb '26

Meta has a problem in its clusters in Boca Raton, Miami; this is affecting the MNA content delivery network and direct content consumption. This has a regional impact in Latin America, since so far most non-cacheable content is consumed from the clusters in Florida. metafixthis.com TCP retransmissions, mediocre performance, ICMP losses [image: image.png]

1 0

Bad glue record in .NET zone
by John Palmer 23 Feb '26

23 Feb '26

Who is in charge of the gtld-servers (for .net)? They have an incorrect glue record for just one of our domains. For the other domains that use that server, the glue record is fine. Can't change it at Network Solutions - they claim the IP is correct.

8 10

OARC 46 Call for Contributions
by Willem Toorop 22 Feb '26

22 Feb '26

This workshop will be a hybrid event. Date - 16-17 May 2026 Location - Edinburgh, Scotland Times - approximately 09:00-16:00 UTC (Local time BST is UTC +1 ) Adjacent to - RIPE 92 (18 - 22 May 2026, https://ripe92.ripe.net/) Deadline for Submissions - 2026-03-06 23:59 UTC https://indico.dns-oarc.net/event/56/abstracts/ All DNS-related subjects and discussion topics are welcome although we're particularly keen to hear more about operational and security related experiences, best practices and practical advice; both for newcomers to the DNS arena and those who have been around for longer who want to learn more about new features and opportunities to improve resilience, security and privacy. (These topics we think will complement the usual high-quality data-based research submissions we always hope to receive!) If you have something interesting to share with the community that lies outside of the focus above, please don't be put off - if it's good, we'll be happy to include it. If you'd like to offer a talk, but are not quite sure what to pick, here's a non-exhaustive list of ideas: 1. *Operations & Deployment* * Configuration management, deployment processes, and interoperability experiences. * Tools, tips, and making effective use of DNS software features. 2. *Performance, Resilience & Scaling* * Provisioning, load-balancing, and planning for resilience. * DNS performance management, efficiency improvements, and metrics. * Monitoring infrastructure: log pipelines, analytics, and anomaly detection. 3. *Security, Privacy & Policy* * DoS attacks, DNS abuse, DNSSEC signing and validation. * Privacy considerations, for example: encrypted transport, qname minimization, data anonymization. * Relevant global and regional policies, legislation, and compliance. 4. *Research & Innovation* * Data-driven testing, measurement, and analysis. * New protocols, protocol extensions, and next-generation namespace management. 5. *Lessons & Learnings* * Outage experiences, recovery stories, and cautionary tales For further details please see https://www.dns-oarc.net/oarc46 Willem Toorop, for the DNS-OARC Programme Committee

1 0

Router Recommendations
by Mike Hammett 21 Feb '26

21 Feb '26

I'm looking for new BGP routers. I'm currently running Mikrotik, which has served me well so far, but looking at interface speed, count, FIB size, etc. and they just aren't going to cut it. I'm looking for: • Has at least 6x 100G ports • Has a smattering of 10G/25G ports • Has meaningful packet buffers • Routes in hardware at least 2m routes combined of IPv4 and IPv6, more is better • Has reasonably low power usage, I don't need 1 kw going to a router • Is cost-effective • Used is fine I like how the MX301 looks, but it's way more than I'd want to spend, primarily because there really isn't a used market for them yet. Arista and Cisco NCS are close, but to check all of the boxes, you're up to about $15k - $20k. To get to $5k or less, you're compromising on at least two of the things I'm looking for. EdgeCore and UfiSpace may have some models that are in the $5k - $8k range, once you purchase OcNOS. I'd have no problem with the EdgeCore and UfiSpace direction, but I wanted to make sure I wasn't leaving anything out of consideration. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

7 11

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 20 Feb '26

20 Feb '26

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 21 Feb, 2026 IPv4 BGP Table (Global) as seen at Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 1035958 Prefixes after maximum aggregation (per Origin AS): 397982 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 510032 Number of IPv4 prefixes with a valid ROA: 616081 Number of IPv4 prefixes with an invalid ROA: 1667 Number of IPv4 prefixes with no ROA: 418210 Total ASes present in the Internet Routing Table: 78009 Prefixes per ASN: 13.28 Origin-only ASes present in the Internet Routing Table: 67003 Origin ASes announcing only one prefix: 27289 Transit ASes present in the Internet Routing Table: 11006 Transit-only ASes present in the Internet Routing Table: 555 Average AS path length visible in the Internet Routing Table: 4.7 Max AS path length visible: 69 Max AS path prepend of ASN (269326) 61 Prefixes from unregistered ASNs in the Routing Table: 1115 Number of instances of unregistered ASNs: 1155 Number of 32-bit ASNs allocated by the RIRs: 48811 Number of 32-bit ASNs visible in the Routing Table: 39910 Prefixes from 32-bit ASNs in the Routing Table: 223005 Number of bogon 32-bit ASNs visible in the Routing Table: 124 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 446 Number of addresses announced to Internet: 3113909760 Equivalent to 185 /8s, 154 /16s and 126 /24s Percentage of available address space announced: 84.1 Percentage of allocated address space announced: 84.1 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: 337475 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 282059 Total APNIC prefixes after maximum aggregation: 82425 APNIC Deaggregation factor: 3.42 Prefixes being announced from the APNIC address blocks: 268566 Unique aggregates announced from the APNIC address blocks: 107033 APNIC Region origin ASes present in the Internet Routing Table: 15075 APNIC Prefixes per ASN: 17.82 APNIC Region origin ASes announcing only one prefix: 4629 APNIC Region transit ASes present in the Internet Routing Table: 1999 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 38 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10630 Number of APNIC addresses announced to Internet: 753245312 Equivalent to 44 /8s, 229 /16s and 156 /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-155961 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: 304460 Total ARIN prefixes after maximum aggregation: 136661 ARIN Deaggregation factor: 2.23 Prefixes being announced from the ARIN address blocks: 303466 Unique aggregates announced from the ARIN address blocks: 146886 ARIN Region origin ASes present in the Internet Routing Table: 19390 ARIN Prefixes per ASN: 15.65 ARIN Region origin ASes announcing only one prefix: 7077 ARIN Region transit ASes present in the Internet Routing Table: 1925 Average ARIN Region AS path length visible: 4.3 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5471 Number of ARIN addresses announced to Internet: 1353025792 Equivalent to 80 /8s, 165 /16s and 137 /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-402332 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, 45/8, 47/8, 48/8, 50/8, 52/8, 54/8, 55/8, 56/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: 284912 Total RIPE prefixes after maximum aggregation: 140862 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 287515 Unique aggregates announced from the RIPE address blocks: 186405 RIPE Region origin ASes present in the Internet Routing Table: 29279 RIPE Prefixes per ASN: 9.82 RIPE Region origin ASes announcing only one prefix: 12173 RIPE Region transit ASes present in the Internet Routing Table: 3985 Average RIPE Region AS path length visible: 4.8 Max RIPE Region AS path length visible: 31 Number of RIPE region 32-bit ASNs visible in the Routing Table: 13075 Number of RIPE addresses announced to Internet: 733096064 Equivalent to 43 /8s, 178 /16s and 40 /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, 53/8, 57/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: 126791 Total LACNIC prefixes after maximum aggregation: 30369 LACNIC Deaggregation factor: 4.18 Prefixes being announced from the LACNIC address blocks: 122547 Unique aggregates announced from the LACNIC address blocks: 49620 LACNIC Region origin ASes present in the Internet Routing Table: 11350 LACNIC Prefixes per ASN: 10.80 LACNIC Region origin ASes announcing only one prefix: 2670 LACNIC Region transit ASes present in the Internet Routing Table: 2534 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 69 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9352 Number of LACNIC addresses announced to Internet: 170987264 Equivalent to 10 /8s, 49 /16s and 15 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-275868 + 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: 36621 Total AfriNIC prefixes after maximum aggregation: 6946 AfriNIC Deaggregation factor: 5.27 Prefixes being announced from the AfriNIC address blocks: 53418 Unique aggregates announced from the AfriNIC address blocks: 19699 AfriNIC Region origin ASes present in the Internet Routing Table: 2018 AfriNIC Prefixes per ASN: 26.47 AfriNIC Region origin ASes announcing only one prefix: 740 AfriNIC Region transit ASes present in the Internet Routing Table: 386 Average AfriNIC Region AS path length visible: 5.3 Max AfriNIC Region AS path length visible: 53 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1382 Number of AfriNIC addresses announced to Internet: 103321600 Equivalent to 6 /8s, 40 /16s and 144 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/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 13814 8945 105 CHINAMOBILE-CN China Mobile Communication 7545 5997 832 548 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5027 4193 77 ERX-CERNET-BKB China Education and Resear 9498 4810 546 335 BBIL-AP BHARTI Airtel Ltd., IN 7552 4070 1332 29 VIETEL-AS-AP Viettel Group, VN 7713 3685 1044 65 TELKOMNET-AS-AP PT Telekomunikasi Indones 56046 3467 887 178 CMNET-JIANGSU-AP China Mobile communicati 45899 3330 1868 99 VNPT-AS-VN VNPT Corp, VN 17561 3141 197 586 LCS-AS-AP LARUS Limited, HK 24560 2981 864 507 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 14342 41157 5584 AMAZON-02 - Amazon.com, Inc., US 22773 4783 3115 365 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 11492 4637 308 1021 CABLEONE - CABLE ONE, INC., US 7155 3861 286 85 VIASAT-SP-BACKBONE - ViaSat,Inc., US 174 3804 8769 865 COGENT-174 - Cogent Communications, LLC, 6327 3699 1321 71 SHAW - Shaw Communications, CA 396982 3322 4856 491 GOOGLE-CLOUD-PLATFORM - Google LLC, US 749 3142 54728 2393 DNIC-AS-00749 - United States Department 16625 2778 1200 2115 AKAMAI-AS - Akamai Technologies, Inc., US 36352 2695 221 892 AS-COLOCROSSING - HostPapa, 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 7238 1711 149 UNI2-AS, ES 39891 4969 306 72 ALJAWWALSTC-AS, SA 20940 3830 3393 113 AKAMAI-ASN1, NL 9009 3796 354 2223 M247, RO 12389 3171 2318 868 ROSTELECOM-AS PJSC Rostelecom. Technical 212238 2626 189 1922 CDNEXT, GB 34984 2443 364 574 TELLCOM-AS, TR 8452 1682 1853 19 TE-AS TE-AS, EG 13188 1607 100 27 TRIOLAN, UA 203020 1606 243 779 HOSTROYALE, IN 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 12689 3306 603 UNINET, MX 10620 3448 457 1103 Telmex Colombia S.A., CO 13999 2465 506 349 Mega Cable, S.A. de C.V., MX 11830 1992 369 65 Instituto Costarricense de Electricidad y 11664 1415 278 33 Techtel LMDS Comunicaciones Interactivas 28573 1375 2430 272 Claro NXT Telecomunicacoes Ltda, BR 3816 1342 770 213 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6147 1254 371 22 INTEGRATEL PERU S.A.A., PE 22884 1058 67 360 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 26615 1056 2483 95 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 24835 1984 648 34 RAYA-AS, EG 36992 1845 1532 339 ETISALAT-MISR, EG 24863 1288 389 16 LINKdotNET-AS, EG 36903 1232 555 98 MT-MPLS, MA 36935 1199 523 46 Vodafone-, EG 37069 1117 1112 11 MOBINIL, EG 29571 1073 78 20 ORANGE-COTE-IVOIRE, CI 20011 580 154 212 NTT-DATA-Inc, ZA 328608 568 47 169 Africa-on-Cloud-AS, ZA 36914 561 82 3 KENET-AS, KE 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 16509 14342 41157 5584 AMAZON-02 - Amazon.com, Inc., US 9808 13814 8945 105 CHINAMOBILE-CN China Mobile Communication 8151 12689 3306 603 UNINET, MX 12479 7238 1711 149 UNI2-AS, ES 7545 5997 832 548 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5027 4193 77 ERX-CERNET-BKB China Education and Resear 39891 4969 306 72 ALJAWWALSTC-AS, SA 9498 4810 546 335 BBIL-AP BHARTI Airtel Ltd., IN 22773 4783 3115 365 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 11492 4637 308 1021 CABLEONE - CABLE ONE, INC., 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 13814 13709 CHINAMOBILE-CN China Mobile Communications Grou 8151 12689 12086 UNINET, MX 12479 7238 7089 UNI2-AS, ES 7545 5997 5449 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5027 4950 ERX-CERNET-BKB China Education and Research Net 39891 4969 4897 ALJAWWALSTC-AS, SA 9498 4810 4475 BBIL-AP BHARTI Airtel Ltd., IN 22773 4783 4418 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 4070 4041 VIETEL-AS-AP Viettel Group, VN 7155 3861 3776 VIASAT-SP-BACKBONE - ViaSat,Inc., 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 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887 - C 396894 UNALLOCATED 8.28.201.0/24 3356 LEVEL3 - Level 3 Parent 13450 UNALLOCATED 8.29.117.0/24 55002 DEFENSE-NET - F5, Inc., 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE - Phonos 395195 UNALLOCATED 8.38.115.0/24 3356 LEVEL3 - Level 3 Parent 1782 UNALLOCATED 8.42.19.0/24 3356 LEVEL3 - Level 3 Parent 13342 UNALLOCATED 12.17.5.0/24 174 COGENT-174 - Cogent Com 26345 UNALLOCATED 12.21.93.0/24 40264 TWC-40264-WI-MN-UPPERMI 396831 UNALLOCATED 12.23.198.0/24 7018 ATT-INTERNET4 - AT&T En 397665 UNALLOCATED 12.24.28.0/24 7018 ATT-INTERNET4 - AT&T En 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 - Hurricane Electric LLC, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.137.48.0/24 Origin: 16904 ARVIG-16904 - Arvig Enterprises Inc., US 23.137.48.0/24 Transit: 3257 GTT-BACKBONE GTT, US 23.137.200.0/24 Origin: 16276 OVH, FR 23.137.200.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.140.216.0/24 Origin: 27176 DATAWAGON - DataWagon LLC, US 23.140.216.0/24 Transit: 20278 NEXEON - Nexeon Technologies, Inc., US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS - Charter Communicat 23.142.24.0/24 Origin: 62164 HEYMMAN-2, CA 23.142.24.0/24 Transit: 64236 UNREAL-SERVERS - UnReal Servers, LLC, 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:14 /10:40 /11:95 /12:298 /13:581 /14:1200 /15:2107 /16:13713 /17:8349 /18:13634 /19:25688 /20:46158 /21:52891 /22:114018 /23:107185 /24:649280 /25:691 /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 8151 6857 12689 UNINET, MX 12479 6166 7238 UNI2-AS, ES 39891 3655 4969 ALJAWWALSTC-AS, SA 11492 3497 4637 CABLEONE - CABLE ONE, INC., US 6327 3479 3699 SHAW - Shaw Communications, CA 22773 3055 4783 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications Inc., US 7155 2820 3861 VIASAT-SP-BACKBONE - ViaSat,Inc., US 16509 2604 14342 AMAZON-02 - Amazon.com, Inc., US 30036 2309 2654 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communications Corp, US 10620 2228 3448 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:1847 2:1556 3:982 4:9 5:5094 6:185 7:6 8:1527 9:26 11:172 12:1224 13:641 14:2696 15:454 16:174 17:399 18:918 20:599 21:4 22:188 23:8174 24:2633 25:2 27:2757 29:19 31:3435 32:32 34:81 35:293 36:4639 37:4459 38:10460 39:1269 40:443 41:4553 42:967 43:2937 44:429 45:19903 46:4932 47:407 48:38 49:2200 50:2080 51:599 52:1280 54:260 55:1112 56:11 57:316 58:2248 59:1432 60:1175 61:3122 62:3130 63:1768 64:6250 65:2121 66:6047 67:3256 68:1493 69:4233 70:1046 71:614 72:3117 74:2979 75:1504 76:590 77:2838 78:1916 79:1790 80:2365 81:2221 82:4017 83:1459 84:2051 85:3831 86:1108 87:2407 88:1344 89:4708 90:811 91:8433 92:2843 93:3017 94:4328 95:4576 96:1445 97:314 98:951 99:790 100:69 101:1338 102:4428 103:32359 104:5527 105:793 106:924 107:2846 108:1227 109:4230 110:2300 111:4164 112:3156 113:1702 114:2180 115:2228 116:2169 117:3463 118:2525 119:2101 120:2707 121:1573 122:2981 123:2338 124:1695 125:3004 126:125 128:1671 129:947 130:1592 131:2345 132:783 133:461 134:1647 135:564 136:1623 137:1410 138:3113 139:1624 140:1832 141:1584 142:2485 143:2181 144:1697 145:628 146:2205 147:2203 148:2793 149:2997 150:1321 151:2695 152:2293 153:927 154:9670 155:2295 156:4601 157:2246 158:1498 159:2767 160:3709 161:1964 162:4028 163:2390 164:2019 165:2619 166:1284 167:2248 168:3991 169:891 170:5537 171:1121 172:4570 173:3448 174:894 175:1352 176:3804 177:4750 178:4371 179:2311 180:3031 181:4416 182:3960 183:2614 184:2004 185:21772 186:5648 187:4883 188:4559 189:4473 190:9739 191:1555 192:11467 193:9600 194:7839 195:5706 196:3284 197:3206 198:6265 199:6140 200:8214 201:6409 202:10822 203:10551 204:4750 205:3812 206:4507 207:4000 208:4363 209:5483 210:4999 211:2778 212:4999 213:4096 214:1074 215:54 216:7206 217:3512 218:1731 219:590 220:2196 221:1316 222:1072 223:3325 End of report

1 0

Reminder to Submit Presentations for NANOG 97
by NANOG Program 20 Feb '26

20 Feb '26

NANOG Community at large, The NANOG Program Committee (PC) would like to remind you that we are now accepting proposals for in-person or live remote presentations at all sessions of NANOG 97, taking place in Bellevue, WA on 01-03 June 2026. Below is a summary of key details and dates from the Call For Content on the NANOG website, which can be found at https://nanog.org/program/call-content/. Requested Topics: We are aiming to spotlight presentations throughout NANOG 97 focusing on Site Reliability Engineering. Topics can range from practical applications in daily troubleshooting to strategic discussions on future network architecture. Potential site reliability engineering topics may include monitoring and observability, incident management, capacity planning, and change management. In addition to the spotlight topic, we are always accepting talks on other topics relevant to our audience. Based on feedback from our recent surveys, we have seen numerous requests for the following topics: - Enterprise Networking - An enterprise network is one with no downstream peers; architecture, challenges, and lessons learned from businesses and campuses large and small - Network Automation - designing networks for AI traffic, recruiting in an AI world, troubleshooting - Hyperscaling - architecture, migration, power concerns - Future of Networking - quantum computing, forecast for changes in technology, design, applications, protocols - Research & Education - what research is happening now in network operations - Security - various protocols and developments, AI implications, RPKI and validators - Optical Networking - technology, practices, deployment options, troubleshooting - Tutorials - from beginner to expert, IPv6, BGP, Segment Routing, DNS, MPLS, VxLAN - See the NANOG Call for Content <https://nanog.org/program/call-content/> for an extensive listing of requested topics We are looking to schedule over 1,700 minutes of content between General Session and Breakout Rooms for NANOG 97, and have confirmed 180 minutes to date - so don’t wait! Presentation abstracts are welcomed now and draft slides should be submitted no later than Monday, 27 April 2026 to be considered for NANOG 97. Presentations may cover current technologies, soon-to-be deployed technologies, and industry innovation. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations should not be promotional or discuss proprietary solutions. The primary speaker, moderator, or author should submit a presentation proposal and abstract via the Program Committee Tool at: https://www.nanog.org/meetings/submit-presentation/ - Sign in with your Profile Account - Select the type of talk you propose to present, and complete the form Timeline for submission and proposal review: - The Submitter will enter the abstract in the Program Committee Tool prior to the deadline for slide submission. - The Program Committee (PC) will perform an initial review and will assign a “shepherd” to help develop the submission, typically within 2 weeks. - The Submitter will develop draft slides of the talk, if not already submitted with the initial proposal. Please submit initial draft slides early — the PC will not evaluate submissions until draft slides are available for review. (NANOG Staff will be available to assist with slide templates upon request from the submitter.) - Panel submissions should provide a document listing bios for the moderator, panelists, and an intended topic list. - The PC will review the slides and will continue to work with the Submitter as needed to develop the topic and content. - DRAFT SLIDE DEADLINE Draft presentation slides should be submitted prior to the published deadline for slides (27 April 2026). - The PC will evaluate submissions to determine presentations for the agenda (to be posted on 04 May 2026). - Submitters will be notified whether their talks have been accepted. - The Agenda will be assembled and posted. - FINAL PRESENTATION SLIDES must be submitted prior to the published deadline for slides (22 May 2026 for in person + live remote presentations). - Lightning talk submissions open for in-person attendees on 31 May 2026. If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the PC ( nanogpc(a)nanog.org) and a representative will respond to you in a timely manner. Otherwise, submit your talk, tutorial, track, or panel proposal to the Program Committee Tool at your earliest convenience. We look forward to reviewing your submission! NANOG 97 Calendar of Events Date Event/Deadline TODAY! CFP Reminder Announcement March 16, 2026 Call for Content Reminder #2 April 20, 2026 Topics List Published April 27, 2026 DRAFT Presentation Slides Due May 04, 2026 Meeting Agenda Published May 22, 2026 FINAL Slides Due May 31, 2026 On-Site Lightning Talk Submissions Open Final slides for accepted presentations must be submitted by Friday, 22 May 2026. Materials received after that date, but prior to 29 May might be accepted based on Shepherd availability, but is not guaranteed. Materials received after 29 May will not be accepted. We look forward to seeing you in June! Sincerely, Adair Thaxton Program Committee Chair Sent on behalf of the NANOG PC

1 0

Call for Presentations (CFP) LAC-PF 2026
by Hernan Moguilevsky 20 Feb '26

20 Feb '26

*1. Introduction* The *Latin American and Caribbean Peering Forum (LAC-PF)* will hold its next edition on *May 11, 2026*, as part of *LACNIC 45*, in the city of *Guadalajara, Mexico*. The objective of LAC-PF is to *promote and provide collaborative spaces* on topics related to *network interconnection*, including Internet Exchange Points (IXPs), CDNs, transport capacity, data centers, and new technologies, among others. The event will have a *limited duration*, and part of the available time will be dedicated to *on-site presentations lasting between 15 and 30 minutes*. For this reason, the *LAC-PF 2026 Program Committee* invites the community to submit proposals to be considered for presentation during the event. ------------------------------------------------------------------------ *2. Topics of Interest* The following list is *non-exhaustive* and represents topics of interest for the proposed presentations: *2.1 Interconnection, peering, and network operations* * Interconnection, peering, routing, and content delivery networks. * Best practices. * Success stories. * IPv6 deployment, RPKI, and route registration at the IXP. * Infrastructure scalability and growth projections. * Peering patterns or profiles. * Challenges in peering. * Interconnection between Internet Exchange Points. * Remote Peering. *2.2 Monitoring, automation, and resilience* * Network monitoring and management. * Security at Internet Exchange Points. * Automation of network device configuration and operations. * Critical systems. * Resilience. * Disaster response. *2.3 Infrastructure and network technologies* * IXP infrastructure. * Data centers. * Optical connectivity at the IXP. * Network technologies for peering: o MPLS o VPLS o VXLAN o EVPN o Segment Routing o SDX *2.4 Services and critical components* * CDN. * Route Servers. * DNS (DNSSEC, IDNs, etc.). * NTP. * New services and applications related to peering. *2.5 New technologies and trends* * Artificial Intelligence. * Artificial intelligence and automation in peering. * Artificial intelligence applied to monitoring and configuration management. * Blockchain. * IoT. * Cybersecurity. * Cloud Computing. * Games. * Video streaming. * Virtual Reality. * Applications or technologies with impact on peering. *2.6 Cooperation and ecosystem* * Cooperation to promote peering. * Synergies among stakeholders: o operators, o academia, o government, o private sector. ------------------------------------------------------------------------ *3. Timeline* The presentation selection process will follow the schedule below: * *Official opening of the Call for Presentations:* January 12, 2026 * *Submission deadline:* March 13, 2026 * *Notification of accepted presentations:* March 27, 2026 * *Deadline for submission of final presentations:* May 4, 2026 ------------------------------------------------------------------------ *4. Submission Conditions* * Accepted languages are: o Spanish, o English, o Portuguese. * Submissions must be provided in one of the following formats: o text, o HTML, o Word, o or PDF/(scanned documents will not be accepted)./ * The submission may: o be accompanied by an article, or o consist solely of the presentation. ------------------------------------------------------------------------ *5. Submission of Proposals* Interested participants must submit their *abstract* within the established deadlines using the following link: Submit new abstract <https://eventos.nog.lat/login/?next=%2Fevent%2F31%2Fabstracts%2F%23submit-a…> This link directs to the *Indico* system. Before submitting an abstract, authors must create a user account if they do not already have one. *Required information:* * Full title of the presentation. * Extended abstract of *200 to 300 words*, with an *absolute maximum of 500 words.* * Name(s) of the author(s). The Program Committee may, at its discretion, request additional or complementary information: * Organization(s) the author(s) belong to or represent. * Photo and short bio of the author(s)/(for presentation purposes)./ * Type of presentation: o Lightning Talk, or o Full Presentation. The *Program Committee* will evaluate and select the submissions and will notify the authors of the accepted presentations so they may submit their final presentation materials. *Thank you,* *Program Committee – LAC-PF 2026* -- Saludos HM

1 0

What's up with BGP communities?
by Ronan Pigott 20 Feb '26

20 Feb '26

Hi, First off, apologies if I'm completely lost. I'm not a network professional of any kind, just a random with a question I can't find the answer to on the internet. Basically, I was poking around on this website called bgp.tools and many ASN have a page describing BGP communities known by the network, e.g. https://bgp.tools/communities/13335. It includes descriptions for each one: > 13335:10106 PoP: bos01 > 13335:10358 PoP: cwb03 > 13335:10712 PoP: den04 > 13335:10766 PoP: maa05 > 13335:10920 PoP: zrh02 > [...] I want to know, where does this supplementary information about the communities come from, in this case the "PoP: blah" bits? I don't think it is communicated by BGP directly, so is there some standard out of band mechanism to describe the communities? Or am I just ignorant of this BGP feature? The background is that I live in AZ, USA, and am I subscribed to Cox for my internet service. I noticed that my ping to "example.com" (literally) is slower on IPv6 compared to IPv4: $ ping -4 example.com PING example.com (104.18.27.120) 56(84) bytes of data. 64 bytes from 104.18.27.120: icmp_seq=1 ttl=251 time=9.58 ms 64 bytes from 104.18.27.120: icmp_seq=2 ttl=251 time=5.94 ms 64 bytes from 104.18.27.120: icmp_seq=3 ttl=251 time=7.76 ms 64 bytes from 104.18.27.120: icmp_seq=4 ttl=251 time=6.85 ms [...] $ ping -6 example.com PING example.com (2606:4700::6812:1b78) 56 data bytes 64 bytes from 2606:4700::6812:1b78: icmp_seq=1 ttl=57 time=20.0 ms 64 bytes from 2606:4700::6812:1b78: icmp_seq=2 ttl=57 time=19.0 ms 64 bytes from 2606:4700::6812:1b78: icmp_seq=3 ttl=57 time=20.8 ms 64 bytes from 2606:4700::6812:1b78: icmp_seq=4 ttl=57 time=19.8 ms [...] $ traceroute -IAen4 -z1 example.com traceroute to example.com (104.18.26.120), 30 hops max, 60 byte packets 1 10.3.0.254 [*] 0.249 ms 0.361 ms 0.362 ms 2 10.40.160.1 [*] 8.978 ms 8.658 ms 7.745 ms 3 100.127.73.232 [*] 6.957 ms 8.557 ms 6.881 ms 4 68.1.0.187 [AS22773] 8.067 ms 10.434 ms * 5 184.183.131.9 [AS22773] 13.818 ms 37.728 ms 17.832 ms 6 162.158.140.23 [AS13335] 16.822 ms 8.761 ms 16.768 ms 7 104.18.26.120 [AS13335] 8.813 ms 7.852 ms 9.451 ms $ traceroute -IAen6 -z1 example.com traceroute to example.com (2606:4700::6812:1b78), 30 hops max, 80 byte packets 1 2600:8800:1780:c000::1 [AS22773] 0.315 ms 0.360 ms 0.362 ms 2 2600:8800:17ff:ffff::1111 [AS22773] 6.601 ms 24.911 ms 9.655 ms 3 2001:578:800:6:8100::818 [AS22773] 31.164 ms 8.727 ms 9.075 ms 4 2001:578:900:4::2 [AS22773] 8.763 ms 7.661 ms 6.873 ms 5 2001:578:1:0:172:17:249:32 [AS22773] 29.991 ms 35.838 ms 19.517 ms 6 2001:578:20:a000::7:1 [AS22773] 21.781 ms 20.676 ms * 7 2400:cb00:12:3:: [AS13335] 20.474 ms 20.099 ms 19.824 ms 8 2606:4700::6812:1b78 [AS13335] 20.078 ms 19.747 ms 20.788 ms It's not really a problem, but still I just want to know... why? I thought it would be kind of odd to have example.com hosted only on IPv4 in the Phoenix area so I was trying to see if I could determine whether or not that was the case looking at https://bgp.tools/communities/13335?show-prefixes=13335%3a10066, but I think there just simply isn't enough information available online for me to find out. Thanks, Ronan

44 122

ISO Frontier Communications or Southern New England Telco (SNET) contact
by Chad Dailey 19 Feb '26

19 Feb '26

Apologies for the noise, I'm stuck... Trying to troubleshoot an apparent congestion / routing(?) / packet loss issue between AS2769 and AS46690 at dayjob. Started on or around Jan 20, just received the report internally today, measurement shows that the issue persists. Additional details available, if you've got a few minutes to spare, or cluebat aimed at the appropriate support portal, I'd appreciate it. Thanks, Chad D

1 0

Re: Geofeeds are adversarial — was Re: Geofeeds are good
by Nicolas Fiumarelli 18 Feb '26

18 Feb '26

Hello all, Interesting discussion, Just to add my grain of sand to the geofeed discussion: At LACNIC, there is already operational support of +5 years for geofeeds aligned with the IETF work in this space ( although adoption is low). RFC 8805 (https://datatracker.ietf.org/doc/html/rfc8805) defines the standard CSV format for geofeeds, and RFC 9632 ( https://datatracker.ietf.org/doc/html/rfc9632) specifies the use of the geofeed: attribute in RPSL objects so that operators can reference their geofeed directly from WHOIS/RDAP data. The 5 RIRs allow to publish geofeeds, format may vary from remarks attribute to geofeed attribute, but in all regions, members can: * Publish geofeed information through MiLACNIC <http://milacnic.lacnic.net>, myApnic, MyArin, etc. * Associate geolocation data with their IP resources. * Make this information publicly available in a structured and machine-readable way. In the case of LACNIC btw you can download the entire geofeed raw file (390 kb) for the region here: https://milacnic.lacnic.net/lacnic/geofeeds This allows operators to provide first-party location data in a standards-based manner, without relying solely on third-party inference. Of course, adoption and operational practices vary, but the functionality is available and aligned with the relevant RFCs. I thought this might be useful context for the ongoing discussion around trust, verification, and the role of RIRs in facilitating accurate geolocation data. Best regards, Nicolás Fiumarelli

1 0