December 2025 - NANOG - lists.nanog.org

IPv4 Pricing
by Mike Hammett 07 Dec '25

07 Dec '25

What are you using for guides for IPv4 pricing? There are a bunch of undated blogs, which don't mean much if there's no date. Hilco's blog says somewhere around $27 for a /22 to /24: https://www.ipv4.global/reports/october-2025/ but then fast forward a month on their auction page and it's down to $22: https://auctions.ipv4.global/prior-sales These guys stopped updating in June: https://ipv4market.eu/ipv4-market-average-sale-prices-2025/ ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

29 86

NANOG 96 Room Block Open + More
by Nanog News 05 Dec '25

05 Dec '25

*** NANOG 96 Room Block Open* ------------------------------------------------------------ *Don’t Get Stuck Peak High San Francisco Prices* Friendly Reminder: Our NANOG 96 room block is filling fast, and once it’s gone… it’s gone. Secure your discounted hotel rate now and lock in your stay for N96. *READ MORE* (https://nanog.org/events/nanog-96/venue/) *** Your Expertise Belongs at NANOG 96* ------------------------------------------------------------ Have a Talk that Pushes Networking Forward? Call for Content! We want it — automation, AI + infra, Kubernetes, optical, security, future-net architecture, research, tutorials, you name it. Bring your expertise to the NANOG stage and help shape the next era of Internet infrastructure. *VIEW NOW* (https://nanog.org/program/call-presentations/) *** Why Network Operators Should Attend NANOG* ------------------------------------------------------------ *Where the Internet’s Future Is Built by Its Community* The most critical conversations about the Internet happen at NANOG conferences. For intermediate, senior, and executive-level technologists, this community isn’t just another tech conference, it’s a place to meet + rub shoulders with the world’s most inspiring minds in Internet infrastructure. *READ NOW* ( https://nanog.org/stories/why-network-operators-should-attend-nanog/) *** 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

1 0

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 05 Dec '25

05 Dec '25

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 06 Dec, 2025 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: 1019924 Prefixes after maximum aggregation (per Origin AS): 394232 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 504455 Number of IPv4 prefixes with a valid ROA: 593473 Number of IPv4 prefixes with an invalid ROA: 1542 Number of IPv4 prefixes with no ROA: 424909 Total ASes present in the Internet Routing Table: 77610 Prefixes per ASN: 13.14 Origin-only ASes present in the Internet Routing Table: 66677 Origin ASes announcing only one prefix: 27126 Transit ASes present in the Internet Routing Table: 10933 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: 69 Max AS path prepend of ASN (269326) 61 Prefixes from unregistered ASNs in the Routing Table: 965 Number of instances of unregistered ASNs: 1004 Number of 32-bit ASNs allocated by the RIRs: 48158 Number of 32-bit ASNs visible in the Routing Table: 39423 Prefixes from 32-bit ASNs in the Routing Table: 217674 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: 439 Number of addresses announced to Internet: 3101066752 Equivalent to 184 /8s, 214 /16s and 134 /24s Percentage of available address space announced: 83.8 Percentage of allocated address space announced: 83.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 333911 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 275935 Total APNIC prefixes after maximum aggregation: 81300 APNIC Deaggregation factor: 3.39 Prefixes being announced from the APNIC address blocks: 263483 Unique aggregates announced from the APNIC address blocks: 106295 APNIC Region origin ASes present in the Internet Routing Table: 14928 APNIC Prefixes per ASN: 17.65 APNIC Region origin ASes announcing only one prefix: 4555 APNIC Region transit ASes present in the Internet Routing Table: 1983 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 39 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10475 Number of APNIC addresses announced to Internet: 753543424 Equivalent to 44 /8s, 234 /16s and 41 /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: 299157 Total ARIN prefixes after maximum aggregation: 134685 ARIN Deaggregation factor: 2.22 Prefixes being announced from the ARIN address blocks: 298844 Unique aggregates announced from the ARIN address blocks: 145729 ARIN Region origin ASes present in the Internet Routing Table: 19388 ARIN Prefixes per ASN: 15.41 ARIN Region origin ASes announcing only one prefix: 7097 ARIN Region transit ASes present in the Internet Routing Table: 1940 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: 5426 Number of ARIN addresses announced to Internet: 1337569152 Equivalent to 79 /8s, 185 /16s and 175 /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: 282405 Total RIPE prefixes after maximum aggregation: 139883 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 283381 Unique aggregates announced from the RIPE address blocks: 183886 RIPE Region origin ASes present in the Internet Routing Table: 29112 RIPE Prefixes per ASN: 9.73 RIPE Region origin ASes announcing only one prefix: 12062 RIPE Region transit ASes present in the Internet Routing Table: 3950 Average RIPE Region AS path length visible: 4.8 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12853 Number of RIPE addresses announced to Internet: 735802752 Equivalent to 43 /8s, 219 /16s and 117 /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: 125940 Total LACNIC prefixes after maximum aggregation: 30804 LACNIC Deaggregation factor: 4.09 Prefixes being announced from the LACNIC address blocks: 121908 Unique aggregates announced from the LACNIC address blocks: 49699 LACNIC Region origin ASes present in the Internet Routing Table: 11324 LACNIC Prefixes per ASN: 10.77 LACNIC Region origin ASes announcing only one prefix: 2678 LACNIC Region transit ASes present in the Internet Routing Table: 2522 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: 9311 Number of LACNIC addresses announced to Internet: 170683904 Equivalent to 10 /8s, 44 /16s and 110 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-274844 + 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: 35522 Total AfriNIC prefixes after maximum aggregation: 6902 AfriNIC Deaggregation factor: 5.15 Prefixes being announced from the AfriNIC address blocks: 51869 Unique aggregates announced from the AfriNIC address blocks: 18465 AfriNIC Region origin ASes present in the Internet Routing Table: 1997 AfriNIC Prefixes per ASN: 25.97 AfriNIC Region origin ASes announcing only one prefix: 734 AfriNIC Region transit ASes present in the Internet Routing Table: 382 Average AfriNIC Region AS path length visible: 5.3 Max AfriNIC Region AS path length visible: 57 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1358 Number of AfriNIC addresses announced to Internet: 103303424 Equivalent to 6 /8s, 40 /16s and 73 /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 13362 8760 123 CHINAMOBILE-CN China Mobile Communication 7545 6048 835 593 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5010 4193 77 ERX-CERNET-BKB China Education and Resear 9498 4602 541 336 BBIL-AP BHARTI Airtel Ltd., IN 7552 4012 1332 28 VIETEL-AS-AP Viettel Group, VN 7713 3711 1044 65 TELKOMNET-AS-AP PT Telekomunikasi Indones 56046 3339 827 183 CMNET-JIANGSU-AP China Mobile communicati 45899 3327 1869 100 VNPT-AS-VN VNPT Corp, VN 24560 2951 864 505 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 140292 2519 276 1939 CHINATELECOM-JIANGSU-SUZHOU-5G-NETWORK CH 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 14280 37210 5402 AMAZON-02, US 22773 4780 3116 369 ASN-CXA-ALL-CCI-22773-RDC, US 11492 4715 313 913 CABLEONE, US 7155 3861 286 85 VIASAT-SP-BACKBONE, US 6327 3691 1320 83 SHAW, CA 396982 3312 4861 486 GOOGLE-CLOUD-PLATFORM, US 749 3208 54760 2459 DNIC-AS-00749, US 16625 2874 1231 2152 AKAMAI-AS, US 36352 2824 231 908 AS-COLOCROSSING, US 174 2703 8768 846 COGENT-174, 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 7282 1711 149 UNI2-AS, ES 39891 4833 298 66 ALJAWWALSTC-AS, SA 9009 4002 376 2294 M247, RO 20940 3862 3395 125 AKAMAI-ASN1, NL 12389 3175 2317 871 ROSTELECOM-AS PJSC Rostelecom. Technical 212238 2533 180 1833 CDNEXT, GB 34984 2423 363 576 TELLCOM-AS, TR 8452 1662 1852 14 TE-AS TE-AS, EG 203020 1612 241 784 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 12651 3291 583 UNINET, MX 10620 3458 463 1101 Telmex Colombia S.A., CO 13999 2508 509 352 Mega Cable, S.A. de C.V., MX 11830 1992 369 65 Instituto Costarricense de Electricidad y 28573 1373 2431 267 Claro NXT Telecomunicacoes Ltda, BR 3816 1344 777 213 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6147 1263 371 22 Telefonica del Peru S.A.A., PE 22884 1056 67 358 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 26615 1016 2486 56 TIM SA, BR 18881 901 1127 31 TELEFONICA BRASIL S.A, 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 1951 506 27 RAYA-AS, EG 36992 1681 1509 399 ETISALAT-MISR, EG 24863 1261 389 20 LINKdotNET-AS, EG 36903 1250 554 97 MT-MPLS, MA 37069 1093 1096 13 MOBINIL, EG 29571 1072 94 22 ORANGE-COTE-IVOIRE, CI 36935 1038 519 32 Vodafone-, EG 20011 580 154 212 NTT-DATA-Inc, ZA 36914 556 82 3 KENET-AS, KE 15399 539 56 51 WANANCHI-, 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 14280 37210 5402 AMAZON-02, US 9808 13362 8760 123 CHINAMOBILE-CN China Mobile Communication 8151 12651 3291 583 UNINET, MX 12479 7282 1711 149 UNI2-AS, ES 7545 6048 835 593 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5010 4193 77 ERX-CERNET-BKB China Education and Resear 39891 4833 298 66 ALJAWWALSTC-AS, SA 22773 4780 3116 369 ASN-CXA-ALL-CCI-22773-RDC, US 11492 4715 313 913 CABLEONE, US 9498 4602 541 336 BBIL-AP BHARTI Airtel Ltd., IN Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 13362 13239 CHINAMOBILE-CN China Mobile Communications Grou 8151 12651 12068 UNINET, MX 12479 7282 7133 UNI2-AS, ES 7545 6048 5455 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 5010 4933 ERX-CERNET-BKB China Education and Research Net 39891 4833 4767 ALJAWWALSTC-AS, SA 22773 4780 4411 ASN-CXA-ALL-CCI-22773-RDC, US 9498 4602 4266 BBIL-AP BHARTI Airtel Ltd., IN 7552 4012 3984 VIETEL-AS-AP Viettel Group, VN 11492 4715 3802 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 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 395195 UNALLOCATED 8.38.115.0/24 3356 LEVEL3, US 1782 UNALLOCATED 8.42.19.0/24 3356 LEVEL3, US 54739 UNALLOCATED 8.44.198.0/23 13335 CLOUDFLARENET, US 13342 UNALLOCATED 12.17.5.0/24 174 COGENT-174, US 26345 UNALLOCATED 12.21.93.0/24 40264 TWC-40264-WI-MN-UPPERMI 396831 UNALLOCATED 12.23.198.0/24 7018 ATT-INTERNET4, 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.135.216.0/24 Origin: 400565 RESERVED, ZZ 23.135.216.0/24 Transit: 3356 LEVEL3, US 23.137.48.0/24 Origin: 16904 ARVIG-16904, 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.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.142.24.0/24 Origin: 62164 HEYMMAN-2, CA 23.142.24.0/24 Transit: 64236 UNREAL-SERVERS, 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:41 /11:94 /12:298 /13:580 /14:1198 /15:2093 /16:13706 /17:8301 /18:13570 /19:25043 /20:45464 /21:52607 /22:113405 /23:105483 /24:637314 /25:697 /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 6852 12651 UNINET, MX 12479 6212 7282 UNI2-AS, ES 11492 3559 4715 CABLEONE, US 39891 3521 4833 ALJAWWALSTC-AS, SA 6327 3478 3691 SHAW, CA 22773 3053 4780 ASN-CXA-ALL-CCI-22773-RDC, US 7155 2820 3861 VIASAT-SP-BACKBONE, US 16509 2434 14280 AMAZON-02, US 30036 2318 2661 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2213 3458 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:1805 2:1541 3:976 4:10 5:4884 6:190 7:6 8:1519 9:6 11:172 12:1230 13:571 14:2640 15:414 16:303 17:388 18:913 20:587 21:4 22:188 23:8092 24:2561 25:2 27:2733 29:19 31:3391 32:32 33:1 34:81 35:288 36:4599 37:4560 38:9377 39:1195 40:446 41:4437 42:949 43:2820 44:398 45:19496 46:5094 47:388 49:2162 50:2051 51:598 52:1567 54:289 55:1102 56:11 57:305 58:2213 59:1388 60:1167 61:3068 62:3098 63:1736 64:5958 65:2128 66:5913 67:3236 68:1499 69:4198 70:1032 71:621 72:3053 74:2934 75:1515 76:603 77:2775 78:1915 79:1784 80:2318 81:2103 82:3828 83:1460 84:2035 85:3649 86:1104 87:2322 88:1350 89:4582 90:838 91:8440 92:2849 93:3013 94:4237 95:4566 96:1448 97:314 98:951 99:773 100:68 101:1340 102:4330 103:32216 104:5525 105:772 106:913 107:2807 108:1212 109:4246 110:2312 111:3979 112:2796 113:1657 114:2101 115:2237 116:2157 117:3136 118:2498 119:2111 120:2409 121:1562 122:2957 123:2288 124:1674 125:2939 126:125 128:1593 129:968 130:1511 131:2261 132:771 133:462 134:1634 135:497 136:1503 137:1209 138:2909 139:1587 140:1779 141:1550 142:2348 143:2143 144:1354 145:627 146:2165 147:2139 148:2790 149:2884 150:1305 151:2617 152:2297 153:767 154:9199 155:2258 156:4251 157:2217 158:1474 159:2693 160:3654 161:1990 162:4007 163:2321 164:1962 165:2615 166:1313 167:2152 168:3888 169:799 170:5455 171:1114 172:4509 173:3428 174:914 175:1342 176:3781 177:4755 178:4299 179:2292 180:2853 181:4349 182:3837 183:2401 184:2060 185:21656 186:5517 187:4784 188:4436 189:4503 190:9707 191:1566 192:11449 193:9508 194:7859 195:5631 196:3298 197:3200 198:6225 199:6093 200:8219 201:6395 202:10674 203:10514 204:4643 205:3730 206:4402 207:3926 208:4267 209:5456 210:4977 211:2772 212:4904 213:4013 214:1027 215:53 216:7064 217:3391 218:1646 219:578 220:2195 221:1286 222:913 223:3213 End of report

1 0

Request for Participation in International Survey on Network Engineering Workforce Development
by MAEMURA Akinori 05 Dec '25

05 Dec '25

Dear colleagues at NANOG, I hope this message finds you well. I'd like to ask you for some help by participating our questionnaire survey: The Japan Network Information Center (JPNIC) and the Ministry of Internal Affairs and Communications (MIC) of Japan are conducting a joint research initiative on the development and retention of network engineering talent. As part of this effort, we are gathering insights from global stakeholders. [Reference] Launch of a Research Study on Securing and Developing Network Engineering Talent, and Request for Cooperation https://www.nic.ad.jp/en/topics/2025/20251205-04.html Japan faces several challenges including regional disparities, shortages of skilled personnel among smaller operators, and gaps in structured training and career development pathways. To inform effective policy development, we seek to learn from your country’s experiences, practices, and ideas. We would be sincerely grateful if you could participate in our international survey on the current status, challenges, and policy approaches related to network engineer development. We plan to share preliminary findings at future forums, and your input will play a meaningful role in shaping this work. The survey can be accessed at the following link: https://www.surveymonkey.com/r/japan-hrd2025 ・Estimated time required: 10-15 minutes ・Survey deadline: December 18 ・Responses will be kept confidential, anonymized during analysis, and used solely for research purposes. ・Any personal information (if provided) will be used only for follow-up communication related to this study. Your expertise and perspectives would be extremely valuable to us. If appropriate, please feel free to forward this invitation to others who may offer relevant insights. Should you have any questions, please do not hesitate to contact us. Thank you very much for your time and cooperation. Best regards, MAEMURA Akinori maem(a)nic.ad.jp Japan Network Information Center (JPNIC) -- MAEMURA Akinori / 前村昌紀 maem(a)nic.ad.jp JPNIC - Japan Network Information Center

1 0

Arista 7280QR-C36 Viability
by Mike Hammett 04 Dec '25

04 Dec '25

At the risk of the Streisand effect, what am I missing about the Arista 7280QR-C36? It looks like a great router for small ISPs (great price, large packet buffers, good port selection, meaningful hardware routes). That said, it looks to be right on the border of DFZ viability. It supports "over 1M" routes, but I currently have about 1,036,824 in my route table. How much over is "over"? What happens in EOS when it goes over? What's the "next best" box for that role? ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

11 15

Cox AS22773 uPRF issue - please contact off list
by Evan S. Weiner 04 Dec '25

04 Dec '25

If there's anyone on here with Cox engineering that can assist with a uPRF strict issue (we're multihomed), please contact me offlist. Thanks, Evan [cid:ca13917c-8f83-46c4-80da-06b0c0d7e178] Evan S. Weiner Managing Member , Hosted Backbone, LLC d: (804) 549-4899<tel:(804)%20549-4899> | m: (804) 677-9544<tel:(804)%20677-9544> e: eweiner(a)hostedbackbone.net<mailto:eweiner@hostedbackbone.net> | w: www.hostedbackbone.net<https://www.hostedbackbone.net/>

5 5

Seeking operator feedback on low-footprint network metadata probe with the goal of open-sourcing
by Fanch FRANCIS 04 Dec '25

04 Dec '25

Hi all, I’m part of a small team that’s been working on network visibility and security for some time now and we ended up developping a software network probe from scratch that we are considering to open-source. Our ask is not really should we, more how much of it? Would any of you use that and how? Now, for a bit of context. For years we have used the usual stack: Zeek plus homegrown glue for databases, dashboards, and so on. That works well enough in many environments (I mean, that’s what META uses for it’s own DC, so it does work alright), but in our own environment… we repeatedly hit limits in a few places: small edge boxes, noisy OT/telco environments, MSP-style multi-tenant deployments, and links where bandwidth drops are painful. At some point we stopped trying to patch more on top of Zeek and started building our own internal network probe instead 6 years ago (time flies by when you code fun stuff). We are now trying to decide how much of it (if any) should be open-sourced, and I’d like to sanity-check that with people who run similar tooling in production. What the probe does (high level) This is NANOG, so a network probe (DPI-based), shouldn’t be strange for a lot of you ;-) For those who are not familiar, it’s a tool that captures packets and turns them into enriched metadata / DB-ready records (flows, protocols, selected network metadata, assets, etc.). Some operational characteristics: * At around 1 Gbit/s sustained line rate, we are currently in the ballpark of: These numbers are still being tuned, but that’s the order of magnitude. * 2 CPU cores and 8GB of RAM * ~10 Mbit/s of metadata sent to the database * ~1 Mbit/s stored on disk after compression That's for the lean part, now for the carrier-grade: * Internal testing, plus commercial test gear (we had it certified by Spirent Communication), shows no false detections at full ine-rate 100 Gbit/s (145.000.000 pps, for around 10 to 12.000.000 news sessions per second) for 135+ network protocols (L2–L7) and nearly 4000+ applications, on simple commodity hardware (no FPGA/ASIC; just good old CPU and RAM). We are not using DPDK. For higher-speed use cases we ended up writing our own NIC drivers in Rust, too. For small links at full line rate with full protocol analysis, resource usage is roughly an order of magnitude lower than what we observed with Zeek or Suricata in equivalent scenarios (happy to share benchmark details if useful). What were our Design goals, in brief: * Low footprint: able to run “where Zeek/Suricata hurt”: on-prem systems, VMs, small Kubernetes worker nodes, cloud workloads, on both small x86 or ARM edge boxes (thanks to Rust), etc. * Simple deployment: a single static Rust binary with no dynamic dependencies. Drop it on a recent Linux host, point it at an interface, and it starts capturing. There is an installer with a CLI mode for use with Ansible/other automation. Optionally, a dockerized DB pipeline for ClickHouse/Postgres. * Fleet-oriented: usable at the scale of hundreds or thousands of probes in an MSP / distributed environment. * Outputs: JSON over HTTP / REST API, plus structured schemas for ClickHouse/Postgres so operators can plug in their own analytics, detections, or reporting. * Implementation: full Rust codebase, with a focus on predictability and safety rather than ad-hoc packet tricks that reduce visibility or telemetry quality. Why we didn’t just stick with Zeek This is not “Zeek bad, our code good”. We simply had a different set of constraints. The main drivers were: * Resource footprint when deploying probes directly on Kubernetes worker nodes, small cloud instances, or ARM edge devices. We also wanted to reuse the same probe design when monitoring much higher-speed links on commodity hardware. * Fleet and multi-tenant operation: the need to deploy, manage, and upgrade a large number of probes in an MSP / MSSP context, with clear separation between tenants. * Tighter control over metadata shape and volume: so that DB / storage does not explode in noisy environments. Our past Zeek deployments filled an Elastic cluster in a couple of days and often forced us to rebuild that instance; we wanted more predictable volume control. The result is a probe that overlaps with Zeek/Suricata functionally, but with different trade-offs. Open source, open core, or something else? Internally we are debating what would actually be useful to open-source for the operator community, versus what (if anything) should remain “product”. The rough options we see: * Open-source the probe engine and protocol parsers, so operators can run and extend it themselves and build their own services / UX on top. * Open-source primarily the DB schemas, ingestion pipeline, and operational tooling, while keeping the probe itself closed. * Keep the entire stack closed and offer it only as a self-hosted / appliance / cloud solution. Before we spend months going down any of these routes, I would really value operator feedback. Specific questions for the readers courageous enough to have reached this point in the post ;-) 1. Does this actually fill a gap for you, or is your current setup “good enough”? If you have deployed Zeek / Suricata / nProbe / NTOP / similar in anger, would you even look at something like this? 2. If some part of it were open-sourced, what would be most useful to you in practice? * Core probe and parsers? * Schemas / ingestion pipeline / deployment tooling? * SDKs / libraries to embed in your own systems? * Something else entirely? 3. Licensing / model concerns: Are there licenses that are an immediate “no” (e.g. AGPL)? Would “core open-source with additional commercial features” be acceptable, or is that a non-starter in your environment? 4. How you would realistically consume it: In your networks, would you be more likely to: * run it as a self-hosted binary on your own infrastructure, * deploy it as some kind of appliance, * or consume it as a managed service that delivers metadata or alerts? 5. What would make you discard it immediately? Examples: excessive resource usage, awkward integration model, unclear security story, problematic license, unclear long-term maintenance, etc. This is not a product announcement, beta signup, or marketing exercise. There are no links in this message. I am trying to avoid spending time open-sourcing the wrong components, or doing it in a way that doesn’t match how operators would actually use such a tool. If you have fought with network telemetry in production, I would appreciate hearing “this would be useful if X/Y/Z” or “we wouldn’t bother, because…”. I am happy to answer technical questions and take blunt feedback, on- or off-list, if this is of interest. Best regards, Fanch Fanch FRANCIS, PhD CEO +33 6 14 60 05 47 https://calendly.com/fanch-nanocorp/visio https://www.nanocorp.ai/<https://141-nanocorp.trakqit.com/?u=https:%2F%2Fwww.nanocorp.ai%2F&e=d4d55a…> [signature_2808701025] [https://141-nanocorp.trakqit.com/img/d4d55ac50f741f8ca2a25dfe80934e92]

1 0

Whatever happened to ONOS?
by Mark Prosser 04 Dec '25

04 Dec '25

I remember quite a long time ago being convinced that ONOS & other SDN projects would change the industry. All the podcasts were suggesting they would as well... Today, in the context of what was promised, they seemingly Still Do Nothing One project I thought was especially interesting was ONOS.... it seemed to really suggest it would transform Telcos in the Whitebox craze timeline. As Openflow and such fell off, I remember ONOS pivoting to SR-TE & PCE... but I haven't heard about it in quite a while. Is anyone using this in production? The websites seem to still exist. https://wiki.onosproject.org/ https://opennetworking.org/onos/ Just curious. Warm regards, -- Mark Prosser // E: mark(a)zealnetworks.ca // W: https://zealnetworks.ca

4 5

OVH (AS16276) peering contact
by Kelly Littlepage 04 Dec '25

04 Dec '25

I'd be grateful if anyone from OVH (AS16276) or someone with a contact at OVH peering could ping me off-list. I can't get a response from the peering-16276(a)ovh.net distro. Cheers, Kelly -- Kelly Littlepage OneChronos Global kelly(a)onechronos.com https://www.onechronos.com -- This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient. If you are not the intended recipient or otherwise believe that you have received this message in error, please notify the sender immediately and delete the original. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If this message was misdirected, OCX Group Inc. does not waive any confidentiality or privilege.

1 0

The NANOG 96 CFP is open through 05-January-2026
by NANOG Program 03 Dec '25

03 Dec '25

NANOG Community at large, The NANOG Program Committee (PC) would like to remind you that we are accepting proposals through Monday, 05 January 2026, for in-person or live remote presentations at all sessions of NANOG 96 taking place in San Francisco, CA on 02-04 February 2026. Our spotlight topic for NANOG 96 is “AI and network infrastructure”, but we accept presentations on all relevant topics. The work you do and the ideas you have are interesting and important, and we’d love to hear more about it! Perhaps you’re having trouble figuring out what the NANOG audience would like to see. During every NANOG Conference, we ask everyone to answer the surveys and tell us what they want to hear about at a future conference. Some of the most recent answers are below. If you have a presentation on any of these general or specific topic areas, your community would love to hear from you! AI / Automation Topics - AI vs “traditional” datacenter networks - Automation approaches - Designing networks for AI traffic - Details on how to define and build AI agents - Network automation technologies - Early-career Professional Development topics - Basic hands-on tutorial track - More career development topics - Emerging technologies topics - More on net infra evolution and the drivers around it - New protocols, technologies, IETF work, etc. - Enterprise Networking Topics - Enterprises interacting with ISPs and the Internet - Overlays - Performance - Open source/freely available tools to move data quickly and efficiently - More information about how to measure and improve network performance from hosts. - Routing / BGP Topics - BGP Route Maps - Integrating IPv6 - Interplanetary networking - More on BGP in data centers like the "lightweight traffic engineering" talk - RPKI, Routing - Peering - Residential Broadband - Segment routing - Researcher / Student Topics - Opportunity for students to network - Researcher / operator BoF / forum - Security Topics - AI-driven botnets and residential proxies - DDoS mitigation topics - Security and IOT - Soft skills - Attracting software developers to network development/engineering - Career development - Computing and internet history - Intro to NANOG mailing list and other operational communities - Risk-based financial decision making - Transitioning from technical roles to management - Troubleshooting and best practices - Layer 2 ethernet best practices - Network architecture or on-prem troubleshooting - Provisioning, troubleshooting - Workshops and How-Tos - More in-depth how-tos / more in-depth seminars - Physical hands on labs - Other - Edge computing - Hardware topics such as ASIC or specific software oriented network engineering - How to start an ISP from scratch - More cloud network specific topics - Starlink - - Submit your 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: NANOG 96 Calendar of Events Date Event/Deadline December 15, 2025 Topics List Published January 05, 2026 DRAFT Presentation Slides Due January 12, 2026 Meeting Agenda Published January 26, 2026 FINAL Slides Due February 01, 2026 On-Site Lightning Talk Submissions Open If you have any questions, 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! Sincerely, Adair Thaxton Program Committee Chair Sent on behalf of the NANOG PC

1 0