January 2026 - NANOG - lists.nanog.org

N96 is Only one Week Away-Attendees Dont Forget This
by Nanog Marketing 23 Jan '26

23 Jan '26

*** N96 Attendees: Don't Forget to Pre-Register for the Workshop!* ------------------------------------------------------- *-----"From Models to Operations: Understanding Autonomous Agents in Networking"* This hands-on workshop is limited to 50 attendees. Pre-registration is required. Once you are registered, please review the pre-requisite preparations page ( https://nanog.org/events/n96-models-to-operations-workshop/pre-requisites/) to ensure you ready to roll on February 3rd. MORE INFO (https://nanog.org/events/n96-models-to-operations-workshop/) https://nanog.org/events/nanog-96/socials/ *** Galentine’s, but Make It Technical* ------------------------------------------------------------ *Women in Tech will Kick Off N96 on Sunday, Feb 1 at 5 pm* Skip the awkward networking and scripted small talk. Join us for "Galentine’s Day," Women in Tech edition, where you can show some love to the women who keep the networks running. No corporate buzzwords. No posturing. Just smart women, real insight, and a little professional love, NANOG-style. 💘 📅 Sunday, Feb. 1 at 5 pm 📍 Seacliff Room, Hyatt San Francisco MORE INFO (https://nanog.org/events/nanog-96/socials/) *** SONiC-VPP and the Power of the Open Source, or…* ------------------------------------------------------------ *How 4,000 Contributors Built “The Inexpensive Glue” Holding Your Network Together* At NANOG, attendees get an inside look at the work shaping real-world networks. At our last conference, one standout example was SONiC-VPP. The session was led by Murali Venkat, a principal engineer at Cisco + Yue Gao (Fred), a software engineer on the project. Click below to learn more. Want to dig even deeper into SONiC-VPP and the work happening at scale? Act fast! NANOG 96 is a little over a week away! Registration is still open ( https://nanog.org/events/nanog-96/register/) for both in-person and virtual attendees. READ MORE ( https://nanog.org/stories/industry-news/sonic-vpp-and-the-power-of-the-open… ) * ** NANOG Socials: Don't Miss Where the Real Conversations Happen--------------------------*----------------------------- *-----Sync Your Calendars to Not Miss our Signature Social, Beer 'N Gear + More!* Some of the most valuable conversations at NANOG don’t happen on stage. They happen over a drink. In a corner of the room. Mid-sentence when someone says, “We ran into the same issue.” LEARN MORE (https://nanog.org/events/nanog-96/socials/) * ** Stay Connected---------------------* --------------------------------------- http://www.facebook.com http://www.instagram.com/nanog_org/ http://www.linkedin.com/company/nanog/ https://www.twitter.com/nanog/ http://nanog.org Elizabeth Drolet Multimedia Content Director eadrolet(a)nanog.org <lbrooks(a)nanog.org> | +1 866-902-1336 | www.nanog.org NANOG | 305 E. Eisenhower Pkwy, Suite 100 | Ann Arbor, MI 48108, USA ASN# 19230

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 23 Jan '26

23 Jan '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 24 Jan, 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: 1029957 Prefixes after maximum aggregation (per Origin AS): 396075 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 507988 Number of IPv4 prefixes with a valid ROA: 609259 Number of IPv4 prefixes with an invalid ROA: 1524 Number of IPv4 prefixes with no ROA: 419174 Total ASes present in the Internet Routing Table: 77820 Prefixes per ASN: 13.24 Origin-only ASes present in the Internet Routing Table: 66875 Origin ASes announcing only one prefix: 27195 Transit ASes present in the Internet Routing Table: 10945 Transit-only ASes present in the Internet Routing Table: 541 Average AS path length visible in the Internet Routing Table: 4.7 Max AS path length visible: 209 Max AS path prepend of ASN (214570) 200 Prefixes from unregistered ASNs in the Routing Table: 1071 Number of instances of unregistered ASNs: 1110 Number of 32-bit ASNs allocated by the RIRs: 48484 Number of 32-bit ASNs visible in the Routing Table: 39705 Prefixes from 32-bit ASNs in the Routing Table: 220983 Number of bogon 32-bit ASNs visible in the Routing Table: 113 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 476 Number of addresses announced to Internet: 3107385984 Equivalent to 185 /8s, 54 /16s and 242 /24s Percentage of available address space announced: 83.9 Percentage of allocated address space announced: 83.9 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: 335794 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 281113 Total APNIC prefixes after maximum aggregation: 82399 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 267306 Unique aggregates announced from the APNIC address blocks: 106940 APNIC Region origin ASes present in the Internet Routing Table: 15027 APNIC Prefixes per ASN: 17.79 APNIC Region origin ASes announcing only one prefix: 4604 APNIC Region transit ASes present in the Internet Routing Table: 1976 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 42 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10582 Number of APNIC addresses announced to Internet: 754797056 Equivalent to 44 /8s, 253 /16s and 74 /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: 301736 Total ARIN prefixes after maximum aggregation: 135438 ARIN Deaggregation factor: 2.23 Prefixes being announced from the ARIN address blocks: 301616 Unique aggregates announced from the ARIN address blocks: 146224 ARIN Region origin ASes present in the Internet Routing Table: 19391 ARIN Prefixes per ASN: 15.55 ARIN Region origin ASes announcing only one prefix: 7061 ARIN Region transit ASes present in the Internet Routing Table: 1918 Average ARIN Region AS path length visible: 4.3 Max ARIN Region AS path length visible: 28 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5446 Number of ARIN addresses announced to Internet: 1344124416 Equivalent to 80 /8s, 29 /16s and 182 /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: 283129 Total RIPE prefixes after maximum aggregation: 140068 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 285031 Unique aggregates announced from the RIPE address blocks: 184980 RIPE Region origin ASes present in the Internet Routing Table: 29153 RIPE Prefixes per ASN: 9.78 RIPE Region origin ASes announcing only one prefix: 12110 RIPE Region transit ASes present in the Internet Routing Table: 3977 Average RIPE Region AS path length visible: 4.8 Max RIPE Region AS path length visible: 209 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12945 Number of RIPE addresses announced to Internet: 734182784 Equivalent to 43 /8s, 194 /16s and 189 /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: 126469 Total LACNIC prefixes after maximum aggregation: 30528 LACNIC Deaggregation factor: 4.14 Prefixes being announced from the LACNIC address blocks: 122100 Unique aggregates announced from the LACNIC address blocks: 49830 LACNIC Region origin ASes present in the Internet Routing Table: 11357 LACNIC Prefixes per ASN: 10.75 LACNIC Region origin ASes announcing only one prefix: 2679 LACNIC Region transit ASes present in the Internet Routing Table: 2526 Average LACNIC Region AS path length visible: 5.3 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: 170604288 Equivalent to 10 /8s, 43 /16s and 55 /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: 36439 Total AfriNIC prefixes after maximum aggregation: 6947 AfriNIC Deaggregation factor: 5.25 Prefixes being announced from the AfriNIC address blocks: 53428 Unique aggregates announced from the AfriNIC address blocks: 19609 AfriNIC Region origin ASes present in the Internet Routing Table: 2018 AfriNIC Prefixes per ASN: 26.48 AfriNIC Region origin ASes announcing only one prefix: 741 AfriNIC Region transit ASes present in the Internet Routing Table: 385 Average AfriNIC Region AS path length visible: 5.3 Max AfriNIC Region AS path length visible: 42 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1380 Number of AfriNIC addresses announced to Internet: 103390208 Equivalent to 6 /8s, 41 /16s and 156 /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 13606 8945 102 CHINAMOBILE-CN China Mobile Communication 7545 6026 833 575 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5029 4193 77 ERX-CERNET-BKB China Education and Resear 9498 4719 543 339 BBIL-AP BHARTI Airtel Ltd., IN 7552 4050 1332 29 VIETEL-AS-AP Viettel Group, VN 7713 3732 1044 65 TELKOMNET-AS-AP PT Telekomunikasi Indones 56046 3420 831 184 CMNET-JIANGSU-AP China Mobile communicati 45899 3332 1868 98 VNPT-AS-VN VNPT Corp, VN 17561 3193 200 621 LCS-AS-AP LARUS Limited, HK 24560 2963 864 512 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 14003 38810 5447 AMAZON-02 - Amazon.com, Inc., US 22773 4778 3115 366 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 11492 4638 308 1020 CABLEONE - CABLE ONE, INC., US 7155 3858 286 85 VIASAT-SP-BACKBONE - ViaSat,Inc., US 6327 3699 1321 71 SHAW - Shaw Communications, CA 396982 3329 4868 499 GOOGLE-CLOUD-PLATFORM - Google LLC, US 174 3184 8768 848 COGENT-174 - Cogent Communications, LLC, 749 3142 54729 2393 DNIC-AS-00749 - United States Department 16625 2819 1209 2121 AKAMAI-AS - Akamai Technologies, Inc., US 36352 2702 222 893 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 9009 3914 366 2239 M247, RO 20940 3832 3393 112 AKAMAI-ASN1, NL 12389 3176 2317 871 ROSTELECOM-AS PJSC Rostelecom. Technical 212238 2559 182 1856 CDNEXT, GB 34984 2425 364 577 TELLCOM-AS, TR 8452 1712 1852 14 TE-AS TE-AS, EG 203020 1609 242 782 HOSTROYALE, IN 13188 1607 100 27 TRIOLAN, UA 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 12672 3304 603 UNINET, MX 10620 3445 457 1107 Telmex Colombia S.A., CO 13999 2483 508 351 Mega Cable, S.A. de C.V., MX 11830 1991 369 65 Instituto Costarricense de Electricidad y 11664 1389 278 33 Techtel LMDS Comunicaciones Interactivas 28573 1375 2430 272 Claro NXT Telecomunicacoes Ltda, BR 3816 1339 770 213 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6147 1258 371 22 INTEGRATEL PERU S.A.A., PE 22884 1056 67 358 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 26615 1016 2486 56 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 1983 646 33 RAYA-AS, EG 36992 1842 1532 339 ETISALAT-MISR, EG 24863 1282 389 16 LINKdotNET-AS, EG 36903 1232 555 98 MT-MPLS, MA 36935 1126 520 42 Vodafone-, EG 37069 1117 1112 11 MOBINIL, EG 29571 1070 78 20 ORANGE-COTE-IVOIRE, CI 20011 580 154 212 NTT-DATA-Inc, ZA 328608 573 49 167 Africa-on-Cloud-AS, ZA 36914 569 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 14003 38810 5447 AMAZON-02 - Amazon.com, Inc., US 9808 13606 8945 102 CHINAMOBILE-CN China Mobile Communication 8151 12672 3304 603 UNINET, MX 12479 7238 1711 149 UNI2-AS, ES 7545 6026 833 575 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5029 4193 77 ERX-CERNET-BKB China Education and Resear 39891 4969 306 72 ALJAWWALSTC-AS, SA 22773 4778 3115 366 ASN-CXA-ALL-CCI-22773-RDC - Cox Communica 9498 4719 543 339 BBIL-AP BHARTI Airtel Ltd., IN 11492 4638 308 1020 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 13606 13504 CHINAMOBILE-CN China Mobile Communications Grou 8151 12672 12069 UNINET, MX 12479 7238 7089 UNI2-AS, ES 7545 6026 5451 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5029 4952 ERX-CERNET-BKB China Education and Research Net 39891 4969 4897 ALJAWWALSTC-AS, SA 22773 4778 4412 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 9498 4719 4380 BBIL-AP BHARTI Airtel Ltd., IN 7552 4050 4021 VIETEL-AS-AP Viettel Group, VN 7155 3858 3773 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 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 395476 UNALLOCATED 12.36.194.0/24 7018 ATT-INTERNET4 - AT&T En 395476 UNALLOCATED 12.36.195.0/24 3356 LEVEL3 - Level 3 Parent 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:93 /12:302 /13:580 /14:1199 /15:2090 /16:13737 /17:8330 /18:13622 /19:25117 /20:45754 /21:52805 /22:113839 /23:106448 /24:645279 /25:692 /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 6832 12672 UNINET, MX 12479 6168 7238 UNI2-AS, ES 39891 3655 4969 ALJAWWALSTC-AS, SA 11492 3498 4638 CABLEONE - CABLE ONE, INC., US 6327 3479 3699 SHAW - Shaw Communications, CA 22773 3049 4778 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications Inc., US 7155 2817 3858 VIASAT-SP-BACKBONE - ViaSat,Inc., US 16509 2476 14003 AMAZON-02 - Amazon.com, Inc., US 30036 2305 2646 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communications Corp, US 10620 2225 3445 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:1840 2:1521 3:962 4:9 5:4956 6:186 7:6 8:1528 9:14 11:172 12:1227 13:620 14:2675 15:415 16:179 17:391 18:917 20:597 21:4 22:188 23:8147 24:2632 25:2 27:2753 29:19 31:3431 32:32 34:81 35:292 36:4642 37:4530 38:9894 39:1256 40:439 41:4543 42:957 43:2907 44:417 45:19706 46:4955 47:403 48:20 49:2192 50:2064 51:599 52:1257 54:238 55:1132 56:11 57:311 58:2231 59:1423 60:1173 61:3111 62:3108 63:1772 64:6203 65:2128 66:6018 67:3257 68:1492 69:4193 70:1031 71:619 72:3096 74:2969 75:1514 76:608 77:2757 78:1922 79:1803 80:2319 81:2133 82:4039 83:1472 84:2026 85:3692 86:1105 87:2392 88:1344 89:4664 90:821 91:8400 92:2861 93:3013 94:4301 95:4527 96:1450 97:314 98:956 99:780 100:69 101:1511 102:4352 103:32333 104:5458 105:785 106:917 107:2823 108:1236 109:4246 110:2309 111:4113 112:3127 113:1704 114:2175 115:2238 116:2167 117:3307 118:2489 119:2110 120:2620 121:1579 122:2973 123:2305 124:1680 125:2987 126:125 128:1656 129:960 130:1571 131:2286 132:770 133:461 134:1622 135:539 136:1627 137:1349 138:2984 139:1608 140:1820 141:1560 142:2468 143:2173 144:1562 145:628 146:2201 147:2270 148:2807 149:2935 150:1323 151:2633 152:2280 153:850 154:9665 155:2305 156:4829 157:2247 158:1500 159:2757 160:3633 161:2005 162:4024 163:2333 164:1971 165:2634 166:1299 167:2213 168:3941 169:902 170:5477 171:1122 172:4569 173:3432 174:892 175:1346 176:3775 177:4744 178:4329 179:2288 180:3014 181:4390 182:3902 183:2540 184:2024 185:21698 186:5551 187:4857 188:4623 189:4460 190:9689 191:1539 192:11484 193:9512 194:7861 195:5697 196:3277 197:3196 198:6234 199:6122 200:8210 201:6401 202:10814 203:10563 204:4748 205:3782 206:4415 207:3972 208:4369 209:5471 210:5012 211:2783 212:4990 213:4055 214:1061 215:54 216:7141 217:3449 218:1675 219:591 220:2191 221:1314 222:1048 223:3281 End of report

1 0

RPKI's 2025 Year in Review
by Job Snijders 22 Jan '26

22 Jan '26

Dear all, Happy new year! Wanna know how RPKI evolved throughout 2025? Read on! :) 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 2024 and 2025 is to look at the absolute numbers. The below table was constructed using data collected by RPKIViews.org between January 1st, 2025 and December 31st, 2025 with the ARIN, AfriNIC, APNIC, LACNIC, and RIPE NCC Trust Anchors. EOY 2024 / EOY 2025 Snapshot differences: ----------------------------------------- 2024-12-31 2025-12-31 ( diff) Total validated cache size (KB): 767,245 923,058 (+ 20%) Total number of files (object count): 415,384 493,707 (+ 19%) Wall time validation run (seconds): 46 35 (- 23%) Wall time without outliner CA (seconds): 26 33 (+ 27%) Publication servers (FQDNs): 53 60 (+ 13%) Certification authorities: 44,935 49,721 (+ 11%) Route Origin Authorizations (ROAs): 280,692 344,209 (+ 23%) Uniq Validated ROA Payloads: 639,900 787,737 (+ 23%) Average ROAIPAddresses per ROA: 2.3 1.8 (- 22%) Unique origin ASNs in ROAs: 47,282 52,661 (+ 11%) IPv4 addresses covered: 2,726,513,768 2,783,187,105 (+ 2%) Uniq IPv4 addresses covered: 1,658,281,248 1,818,913,944 (+ 10%) IPv6 addresses covered: 17,392 * 10^30 18,684 * 10^30 (+ 7%) Uniq IPv6 addresses covered: 15,139 * 10^30 16,384 * 10^30 (+ 8%) Unique ASPA Customer ASIDs: 87 556 (+539%) The number of IP addresses covered by RPKI ROAs grew by 10%. This is similar to last year's report. However, ASPA object count absolutely skyrocketed in 2025! The "Uniq ASPA Customer ASIDs" field is a simple gauge counter for global ASPA deployment on the signer side. At the moment of writing, for about 0.5% of Autonomous Systems in the Internet global routing system an ASPA record is published. That's a very interesting development. The ability to publish ASPA objects became readily available [4] in the RIPE NCC region in 2025, and as of January 2026 also fully available through ARIN Online [5]. The "Wall time validation run (seconds)" metric is produced by revalidating the data contained in the two snapshots multiple times in a benchmark using the same modern multi-threaded RPKI cache implementation on the same 4 CPU core machine, without performing any network operations (i.e. offline validation mode). This metric relates to the hypothesis that as the RPKI grows (in size and number of objects), without also improving efficiency (information density), the overall processing time to validate the complete dataset will increase. This year's benchmark environment: Rpki-client 9.7, OpenSSL 3.5.4, Debian 13, on Intel Xeon. WITH EVERY RPKI CA, FIRST 2024 THEN 2025: $ hyperfine -w2 'rpki-client -p4 -P 1735689171 -n -d rpki-20241231T235251Z/data /tmp' Time (mean ± σ): 46.514 s ± 0.172 s [User: 173.345 s, System: 5.264 s] Range (min … max): 46.257 s … 46.756 s 10 runs $ hyperfine -w2 'rpki-client -p4 -P 1767225374 -n -d rpki-20251231T235614Z/data /tmp' Time (mean ± σ): 35.046 s ± 0.206 s [User: 125.092 s, System: 5.894 s] Range (min … max): 34.756 s … 35.444 s 10 runs FIRST 2024 THEN 2025, WITHOUT THE OUTLINER CA: 20241231T235251Z: Time (mean ± σ): 26.257 s ± 0.152 s [User: 92.878 s, System: 4.590 s] Range (min … max): 26.069 s … 26.485 s 10 runs 20251231T235614Z: Time (mean ± σ): 32.903 s ± 0.143 s [User: 117.059 s, System: 5.444 s] Range (min … max): 32.635 s … 33.127 s 10 runs This year the "wall time" metric _seemingly_ deflated... but, unfortunately, further sleuthing shows that the 2024 numbers were heavily skewed by the products issued by a specific large CA under ARIN, an outliner so to speak. In the 2024 snapshot that one CA had 50,125 Manifest entries and 15,944 CRL entries, while in the 2025 snapshot the same CA had 48,896 Manifest entries and only 33 CRL entries. The key observation here is that the impact of large CRLs becomes more pronounced with longer Manifests. In conclusion and discounting the products of that one outliner CA, overall processing time of the RPKI increased by 25%. [ Note: the wall time metric is not comparable between successive annual reports (for example, next year I might use a different computer, or use a different validator implementation) - but within the context of a single annual report the comparison between the snapshots is apples to apples! ] The "Average ROAIPAddresses per ROA" metric shows how many IP prefixes, on average, are contained within a single ROA object. The higher the number of ROAIPAddresses per ROA is, the higher computational efficiency likely is to be. "Efficiency" in this context is viewed as how many ROAIPAddress entries are packed together and signed with a single EE certificate. A higher number means more efficiency (and less RP bandwidth consumption) The RIPE NCC hosted CA system yields 6.6 prefixes per ROA, while the current ARIN and LACNIC approach result in only 1.1 and 1.3 prefixes per ROA, respectively (almost the worst possible case). APNIC and its community lead in efficiency with 8.2 per ROA. The impact that CA implementation choices have on the RPKI's scalability remains an area of concern: large CA operators (such as the RIRs) need to take special care when deciding on parameters such as ROAIPAddress packing and certificate validity periods, in order to curb uneconomical Manifest & CRL growth. Issuing RPKI objects aiming for high information density helps improve predictable delivery trajectories towards relying parties. Statistics on accumulating counters throughout the year: -------------------------------------------------------- The following statistics were produced using the RPKIViews 2024 Amalgamation [6] and RPKIViews 2025 Amalgamation [7] datasets. I believe these datasets to be a near complete collection of all signed RPKI data produced in those years. Almost every ROA! The objects in the Zenodo hosted archives can be inspected with "rpki-client -jf" (filemode). 2024 2025 Number of Rpkiviews snapshots produced: 64,923 90,523 (+ 39%) Newly discovered RPKI objects: 56,586,149 61,524,413 (+ 9%) Avg number of new objects per second: 1.79 1.98 (+ 10%) Median object size (bytes): 1,924 1,924 ( -) Mean object size (bytes): 2,193 2,531 (+ 15%) Cumulative size of all objects (KB): 121,211,067 152,094,584 (+ 25%) The above numbers can be used to better understand RPKI transport protocol efficiency. More on that next year! IETF SIDROPS - Working Group developments ========================================= Some fun updates from the IETF working group responsible for development and maintenance of the RPKI technology stack... *** SIDROPS ***. This RPKI-focused design & implementation group now operates with a new charter. The most significant change in modus operandi being that RFC publication now requires multiple implementations to exist and interoperate. Read the full charter here: https://datatracker.ietf.org/wg/sidrops/about/ ASPA - where we at? ------------------- Close to Working Group Last call! Depending our luck this might mean the specifications are published in late 2026. Word on the streets is that various commercial-off-the-shelf/hardware vendors are working on ASPA implementations, and a number of BGP open source projects already made ASPA verification implementations available to the wider public. Other (New) Work in SIDROPS --------------------------- 1/ A new scalable data synchronisation protocol called Erik Synchronisation is in the works. It is a HTTP-based protocol using Merkle trees, a content-addressable naming scheme, and concurrency control using monotonically increasing sequence numbers. https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-rpki-erik-protocol 2/ What MRT Tabledumps meant for researching BGP, is what CCR is intended to be for the RPKI. CCR (Canonical Cache Representation) is a new small and efficient binary file format to record validation outcomes and hash markers. https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-rpki-ccr SIDROPS Finished work --------------------- One new clarification RFC was published: * RFC 9829 - Handling of Resource Public Key Infrastructure (RPKI) Certificate Revocation List (CRL) Number Extensions https://www.rfc-editor.org/rfc/rfc9829.html Small Point On Housekeeping: ============================ The RPKIViews archive data collection approach and structure were revised at the start of 2026. A number of rpkiviews gatherer nodes now use a Tar+Zstandard spooling system to store raw data and associated snapshots in Canonical Cache Representation format. The changes in how RPKIviews data is stored should have a positive effect, meaning more snapshots can be gathered per hour while at the same time consuming less disk storage space than previously. I'm curious to see what this increase in data resolution might show us next year! Final words =============================================================== The RPKI remains an important tool in the toolbox to identify & prevent routing incidents. Deployment of RPKI allows operators to improve network reliability by strengthening the security and integrity of their interconnection with the global Internet routing system. The system is working pretty good and will continue to serve us well if special care is taken to continually monitor and optimize the RPKI's data packing practises & delivery methods. Kinds regards, Job Snijders ps. Shout out to Lee Hetherington, Matsuzaki "maz" Yoshinobu, Niels Bakker, Jeroen Lauwers, Jeroen Massar, Digital Ocean, and Tom Scholl for their help to the RPKIViews.org project. References: RPKIViews - http://www.rpkiviews.org/ https://dango.attn.jp/rpkidata/2024/12/31/rpki-20241231T235251Z.tgz https://josephine.sobornost.net/rpkidata/2025/12/31/rpki-20251231T235614Z.t… Last year's report: https://blog.apnic.net/2025/01/28/rpkis-2024-year-in-review/ 2023 report: https://labs.ripe.net/author/job_snijders/rpki-2023-review-growth-governmen… [4]: https://labs.ripe.net/author/tim_bruijnzeels/aspa-in-the-rpki-dashboard-a-n… [5]: https://www.arin.net/announcements/20260120/ [6]: Snijders, J., "RPKIViews 2024 Amalgamation". Zenodo. https://doi.org/10.5281/zenodo.18328474 [7]: Snijders, J., "RPKIViews 2025 Amalgamation". Zenodo. https://doi.org/10.5281/zenodo.18332099

1 0

Looking for a /16 ip space
by Brandon Z. 22 Jan '26

22 Jan '26

Hi all, I have a friend who is currently looking to buy a /16 IPv4 subnet. Please see the requirements below: - Preference: Transfer to RIPE. - Acceptable Regions: RIPE, APNIC, or ARIN blocks. Please reach out to me directly if you have an offer or any leads. On a side note, does anyone happen to know if Cogent sells legacy resources? Best regards, *Brandon Z.* HUIZE LTD www.huize.asia <https://huize.asia/>| www.ixp.su | Twitter This e-mail and any attachments or any reproduction of this e-mail in whatever manner are confidential and for the use of the addressee(s) only. HUIZE LTD can’t take any liability and guarantee of the text of the email message and virus.

3 2

Microsoft contact - emails being blocked from our app to our users
by Erik Levinson 21 Jan '26

21 Jan '26

Hello, does anyone have a Microsoft contact that could help with an email deliverability issue that started approximately two days ago? We (LeapAP) are seeing a large and increasing volume of mail errors from Microsoft, such as the below (XXXX is our dedicated IP at our ESP) and are unable to deliver mail to our users with the following destination domains (so it seems like the hosted Office 365 domains aren't impacted, but only the free/Outlook.com ones): hotmail.com hotmail.ca live.ca msn.com outlook.com live.com 4.7.650 The mail server [XXXX] has been temporarily rate limited due to IP reputation. For e-mail delivery information, see https://aka.ms/postmaster (S775) SNDS shows nothing abnormal for the IP address during the involved time period or earlier, but I can only see up to yesterday @ 18:00 PT there. We submitted the Microsoft form at https://olcsupport.office.com/ and have a ticket number as a result, which I can share as well. Appreciate the help as we're quite impacted and getting a lot of support tickets. Thanks Erik Levinson LeapAP

1 0

Apply Today for the ARIN 57 Fellowship Program
by John Sweeting 21 Jan '26

21 Jan '26

Hello NANOG, Please see the announcement below referencing ARIN's Fellowship Program. ________________________________ From: ARIN-announce <arin-announce-bounces(a)arin.net> on behalf of ARIN <info(a)arin.net> Sent: Thursday, January 8, 2026 10:26 AM To: arin-announce(a)arin.net Subject: Apply Today for the ARIN 57 Fellowship Program Interested in Internet governance, number resource policy, and getting involved in the ARIN community? Become an ARIN Fellow! Applications for the ARIN 57 Fellowship Program are now open, and we encourage you to apply for this specialized, interactive learning opportunity. https://www.arin.net/beafellow Applications are now being accepted through 26 January 2026.  What to Expect Selected Fellows will participate in virtual sessions before and after the ARIN 57 Public Policy and Members Meeting held 19-22 April 2026 in Louisville, Kentucky, and online. Fellows may attend ARIN 57 either in person or virtually, as determined by the Fellowship Selection Committee. With the personal support from experienced ARIN community Mentors, Fellows will have the opportunity to: - Ask questions and receive feedback, - Gain the knowledge and confidence to join in community discussions and contribute new ideas, and - Become part of the future of Internet governance and policy in the ARIN region.  Who Should Apply Individuals who are 18 years of age or older and reside in the ARIN region (https://www.arin.net/about/welcome/region/) are eligible to apply if they have a demonstrated interest in the ARIN community and its Policy Development Process for the management of Internet number resources.   Applicants should understand the importance of ARIN’s mission and be familiar with ARIN services, the Internet number resources it manages, and the processes reflected in the Number Resource Policy Manual (NRPM) (https://www.arin.net/participate/policy/nrpm/)   To learn more about ARIN’s Fellowship Program, the selection process, and the Terms and Conditions, please visit ARIN’s Fellowship Program portal (https://www.arin.net/fellowships) Applicants can email fellowships(a)arin.net<mailto:fellowships@arin.net> for more information or to request a customizable letter to their employer that highlights the benefits of taking part in ARIN’s Fellowship Program.  ARIN looks forward to receiving your application soon!  Regards,  Amanda Gauldin Senior Project Manager American Registry for Internet Numbers (ARIN)

1 0

pingability of 2600::
by Marco Moock 20 Jan '26

20 Jan '26

Hello! Cogent operates a machine on 2600::. IIRC there was also a route to sprint for that net, but that seems to be gone. I can ping that via my ISP (AS8820) that uses Cogent as its current default uplink. Although, I cannot ping that from various other ISPs, e.g. HE AS6939 or DTAG 3320 (no route). Some other people reported issues years ago: https://www.reddit.com/r/ipv6/comments/1bzfqzn/2600_is_no_longer_pingable/ Do some people know more about that case? -- kind regards Marco Send unsolicited bulk mail to 1768504259muell(a)stinkedores.dorfdsl.de

5 8

New c-nsp, j-nsp, a-nsp, etc mailing lists
by Drew Weaver 20 Jan '26

20 Jan '26

I was a big fan of the *-nsp(a)puck.nether.net<mailto:*-nsp@puck.nether.net> mailing lists that now seem to be completely gone without any indication of whether or when they might return. I've been considering just setting up new ones. Please email me off-list if you think this might be useful. Thanks, -Drew

15 25

TORNOG 1 -- Call for Proposals
by Mark Prosser 20 Jan '26

20 Jan '26

Hello NANOG community, Our little community NOG, here in Toronto, is growing. This year we are hosting our first ever full day conference on April 13th, 2026. We would like to welcome folks from far & wide to submit proposals and bring content to operators within our region. The Proposal window opened today. It will be open until EOD (23:59:59 EDT) on March 6th, 2026. We are looking for technical or "meta" talks on networking, automation, and observability. Yet, we also welcome our infrastructure peers to discuss their perspectives on the network. Talks can be 10 minutes, 30 minutes, or 45 minutes in length (technical tutorial / deep dives). Please provide your abstract, speaker bio (optional), and preferred talk length. Slides are not required but appreciated. The theme of TORNOG 1 is: "Stories from Regional Operators" Talks that will be regional to the Toronto / Ontario area will be highly considered. But we would also consider other regional stories from across Canada, and beyond, that consider their story useful to operators in the Toronto area. However, this is just a theme. Talks on any subject, that are not marketing focused, will be considered. Some topics to consider: - Network Automation - Observability & Telemetry - Network Security - Cloud Networking - Career Development in Networking - Diversity & Inclusion in Tech - Emerging Technologies in Networking - Segment Routing / Traffic Engineering - AI & Machine Learning in Networking - Case Studies / Postmortems Please sends you talks to talks(a)tornog.ca or follow the link at: https://tornog.ca/events/tornog-1/proposals/ I wish you all a wonderful 2026, full of peace & prosperity. We are also looking for Sponsors for TORNOG 1. Please reach out to us at sponsors(a)tornog.ca to receive details on our propspectus. We would also appreciate proposals from organizations willing to collaborate with us on workshops -- free with base ticket purchase -- on April 14th, 2026. We hope this would add value for operators traveling into Toronto or clearing their calendar to participate in our community. Some of the TORNOG team will be at NANOG96, if you'd like to learn more over a beer or an in-N-out burger. In solidarity, Mark Prosser Designated TORNOG Lead & Network Operator Advocate /* P.S. -- I have used my BDFL powers to price our tickets at a level I believe is accessible to operators from many walks of life; however, if you feel you the price is out of reach for you, please do not hesitate to reach out & I will do my best to make an accommodation for you. */

1 0

Optimizing Singapore peering?
by Landy Bible 19 Jan '26

19 Jan '26

Hey NANOG, I realize this is "NA" NOG list, but I assume I'm not the only one here who is operating a global network. Context: we have a dozen or so PoPs around the world to serve our load balancer product. We're using continent-specific prefixes to run anycast for this. We are on at least one IX at each location, and use Cogent as our primary transit provider. We'd like to add a real Tier 1 provider at each pop in the future, but In general, this all works ok right now. However, Singapore is a problem. We're on SGIX, but we're seeing a rather high percentage of traffic that originates in Singapore entering our Tokyo PoP instead. Google Cloud in particular is REALLY bad, with application latency testing approaching nearly 1 second, when our typical global latency is under 100ms on an end to end test. Other SG clouds are bad, but not THAT bad. My question to the list here is... for those of you who also operate in Singapore... what would you suggest we do to improve things here? We're looking at adding Arelion or NTT transit in APAC, but we're also trying to get PNIs (or even full IP transit) to the big Singapore networks like SingTel, SingNet, and StarHub, but we haven't had any luck yet. Perhaps we just don't know the right people. From a business perspective our primary concern is latency for our big customers who are hosted on the clouds in the area, but I don't want to just ignore our other customers who aren't in the cloud. Based on my research thus far, my gut says getting transit from Arelion is probably my best "bang for buck" move, but I'm wondering if any of you have any insights or wisdom to share about Singapore or APAC in general. Thanks All, Landy AS62902

6 5