November 2025 - NANOG - lists.nanog.org

DHCP v6 for IPv4 Delegated prefrefix - Wan IPv6 Only to be routed with RFC8950
by Douglas Fischer 12 Nov '25

12 Nov '25

Trying to stay focused on IPv4 as a Service... I dream of being able to build a backbone that is truly IPv6 Only! But even taking some steps in 464xlat environments, there are still commercial demands that still impose the use of Dual-Stack. This is the case with clients who require (and pay for) a routed IPv4 address. I've been looking for a solution for some time to deliver a routed IPv4 address to the client, and to do so in a way that doesn't depend on exchanging information via email and similar means to let the client know which IPv4 block to use. Note 1: Almost all are business subscribers, and 95% of the time they purchase the delivery of an IPv4 /32 address as a service. In cases where we had access to the device, we frequently used DHCP IPv4 Option 121, pointing the routed block (/32, /31, or even /29) with the next-hop of the route pointing to the same IP address on the subscriber's side of the /30 link network with private IPs. The complex part is that the subscriber's "IT Guy" needs to have a minimum understanding of networking and know that they have to use those IPs as needed. In most cases, this is done in a loopback network, to be used as a VPN endpoint, for NAT... And in very rare cases, routed to the client's internal network to be used as a loopback for servers and similar things. We even developed some JerryRig scripts to retrieve this route information taught via DHCP IPv4 Option 121 and "semi-automate" the use of these IPs in loopbacks in address lists to facilitate client use. But this is only possible on CPEs where scripting is allowed, and even then it's a big challenge to handle multiple NOS on CPEs. My current goal is to find a way to deliver an IPv4 prefix to the subscriber and tell it, "This IPv4 block is delegated to you, and you use it as you see fit... And the default IPv4 route is the same IP as the default IPv6 route." Note2: I tried doing this with the 6PE format 0:0:0:0:0:ffff:IPv4_Block. But I haven't had success with common CPEs. I feel there's a good chance I'm reinventing the wheel. And this is already handled in some DHCPv6 options. And that's precisely why I'm asking my colleagues here if there's already something that can help me. If there isn't... Trying to keep the focus on IPv4 as a Service... Would it be too much to dream of setting something like that up? Note 3: I even considered JerryRiging the JerryRig. That would be a way to "teach via DHCPv6" that these clients have to establish a BGP session over IPv6 with IPv4 and IPv6 Address-Families. But I didn't see that this would help much in putting IPv4 in the loopback of the CPEs. So I left that aside. Any colleagues with suggestions on how to solve this type of problem? P.S.: Unfortunately, my customer base is still far from being able to do without IPv4. And handling things within the client's network IS NOT AN OPTION! Just like "464XLAT 1:1" isn't an option either due to the specific demands of the clients. -- Douglas Fernando Fischer Engº de Controle e Automação

4 6

Spoofer Report for NANOG for Oct 2025
by CAIDA Spoofer Project 10 Nov '25

10 Nov '25

In response to feedback from operational security communities, CAIDA's source address validation measurement project (https://spoofer.caida.org) is automatically generating monthly reports of ASes originating prefixes in BGP for systems from which we received packets with a spoofed source address. We are publishing these reports to network and security operations lists in order to ensure this information reaches operational contacts in these ASes. This report summarises tests conducted within usa, can. Inferred improvements during Oct 2025: ASN Name Fixed-By 54334 ROYA 2025-10-27 273143 2025-10-29 21804 ACCESS-SK 2025-10-30 12183 TALKIE-COMMUNICATIONS 2025-10-31 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Oct 2025: ASN Name First-Spoofed Last-Spoofed 27364 ACS-INTERNET 2016-09-27 2025-10-13 393397 LREC-LRT 2020-08-02 2025-10-24 22773 ASN-CXA-ALL-CCI-22773-RDC 2021-10-24 2025-10-28 12183 TALKIE-COMMUNICATIONS 2022-12-10 2025-10-07 400282 2023-04-27 2025-10-30 393577 SCCNET 2023-05-03 2025-10-28 61461 Airtek Solutions C.A. 2023-05-13 2025-10-23 394684 WISPERNET 2024-01-17 2025-10-31 53755 IOFLOOD 2024-02-23 2025-10-31 393530 TLU 2024-05-22 2025-10-26 19935 CRRS 2024-05-29 2025-10-14 27523 DMB-ASN 2024-11-15 2025-10-23 273143 2025-03-01 2025-10-29 273843 2025-04-02 2025-10-24 54334 ROYA 2025-07-30 2025-10-30 47583 AS-HOSTINGER 2025-09-27 2025-10-29 21743 ANL-36 2025-10-03 2025-10-06 273595 2025-10-06 2025-10-06 23316 BAI-IP-SERVICES 2025-10-16 2025-10-16 214639 2025-10-22 2025-10-29 204969 AS_CIRTEL 2025-10-22 2025-10-22 398493 2025-10-23 2025-10-23 17290 BLUE-MOUNTAIN 2025-10-29 2025-10-29 Further information for these tests where we received spoofed packets is available at: https://spoofer.caida.org/recent_tests.php?country_include=usa,can&no_block… Please send any feedback or suggestions to spoofer-info(a)caida.org

2 2

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 10 Nov '25

10 Nov '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 08 Nov, 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: 1012261 Prefixes after maximum aggregation (per Origin AS): 392668 Deaggregation factor: 2.58 Unique aggregates announced (without unneeded subnets): 501148 Number of IPv4 prefixes with a valid ROA: 580581 Number of IPv4 prefixes with an invalid ROA: 1523 Number of IPv4 prefixes with no ROA: 430157 Total ASes present in the Internet Routing Table: 77510 Prefixes per ASN: 13.06 Origin-only ASes present in the Internet Routing Table: 66548 Origin ASes announcing only one prefix: 27117 Transit ASes present in the Internet Routing Table: 10962 Transit-only ASes present in the Internet Routing Table: 545 Average AS path length visible in the Internet Routing Table: 4.7 Max AS path length visible: 57 Max AS path prepend of ASN ( 37447) 53 Prefixes from unregistered ASNs in the Routing Table: 955 Number of instances of unregistered ASNs: 993 Number of 32-bit ASNs allocated by the RIRs: 47936 Number of 32-bit ASNs visible in the Routing Table: 39257 Prefixes from 32-bit ASNs in the Routing Table: 215103 Number of bogon 32-bit ASNs visible in the Routing Table: 106 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 416 Number of addresses announced to Internet: 3103608960 Equivalent to 184 /8s, 253 /16s and 80 /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: 332336 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 271861 Total APNIC prefixes after maximum aggregation: 81017 APNIC Deaggregation factor: 3.36 Prefixes being announced from the APNIC address blocks: 261631 Unique aggregates announced from the APNIC address blocks: 106371 APNIC Region origin ASes present in the Internet Routing Table: 14871 APNIC Prefixes per ASN: 17.59 APNIC Region origin ASes announcing only one prefix: 4535 APNIC Region transit ASes present in the Internet Routing Table: 1974 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 34 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10418 Number of APNIC addresses announced to Internet: 749209856 Equivalent to 44 /8s, 168 /16s and 9 /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: 297841 Total ARIN prefixes after maximum aggregation: 133772 ARIN Deaggregation factor: 2.23 Prefixes being announced from the ARIN address blocks: 298000 Unique aggregates announced from the ARIN address blocks: 145257 ARIN Region origin ASes present in the Internet Routing Table: 19375 ARIN Prefixes per ASN: 15.38 ARIN Region origin ASes announcing only one prefix: 7099 ARIN Region transit ASes present in the Internet Routing Table: 1948 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: 5406 Number of ARIN addresses announced to Internet: 1345179904 Equivalent to 80 /8s, 45 /16s and 209 /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: 281173 Total RIPE prefixes after maximum aggregation: 139513 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 281804 Unique aggregates announced from the RIPE address blocks: 182449 RIPE Region origin ASes present in the Internet Routing Table: 29099 RIPE Prefixes per ASN: 9.68 RIPE Region origin ASes announcing only one prefix: 12102 RIPE Region transit ASes present in the Internet Routing Table: 3968 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: 12799 Number of RIPE addresses announced to Internet: 735294848 Equivalent to 43 /8s, 211 /16s and 181 /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: 125439 Total LACNIC prefixes after maximum aggregation: 30778 LACNIC Deaggregation factor: 4.08 Prefixes being announced from the LACNIC address blocks: 121485 Unique aggregates announced from the LACNIC address blocks: 49486 LACNIC Region origin ASes present in the Internet Routing Table: 11311 LACNIC Prefixes per ASN: 10.74 LACNIC Region origin ASes announcing only one prefix: 2660 LACNIC Region transit ASes present in the Internet Routing Table: 2532 Average LACNIC Region AS path length visible: 5.4 Max LACNIC Region AS path length visible: 38 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9288 Number of LACNIC addresses announced to Internet: 170739456 Equivalent to 10 /8s, 45 /16s and 71 /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: 34992 Total AfriNIC prefixes after maximum aggregation: 6928 AfriNIC Deaggregation factor: 5.05 Prefixes being announced from the AfriNIC address blocks: 48925 Unique aggregates announced from the AfriNIC address blocks: 17218 AfriNIC Region origin ASes present in the Internet Routing Table: 1983 AfriNIC Prefixes per ASN: 24.67 AfriNIC Region origin ASes announcing only one prefix: 721 AfriNIC Region transit ASes present in the Internet Routing Table: 378 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: 1346 Number of AfriNIC addresses announced to Internet: 102961920 Equivalent to 6 /8s, 35 /16s and 19 /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 13466 8760 120 CHINAMOBILE-CN China Mobile Communication 7545 6094 833 590 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4967 4193 77 ERX-CERNET-BKB China Education and Resear 9498 4518 538 315 BBIL-AP BHARTI Airtel Ltd., IN 7552 3980 1332 28 VIETEL-AS-AP Viettel Group, VN 7713 3720 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3319 1869 99 VNPT-AS-VN VNPT Corp, VN 56046 3246 827 182 CMNET-JIANGSU-AP China Mobile communicati 24560 2941 864 506 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 140292 2493 274 1922 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 14312 37278 5387 AMAZON-02, US 11492 4780 317 801 CABLEONE, US 22773 4640 3108 403 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3861 286 85 VIASAT-SP-BACKBONE, US 6327 3671 1320 82 SHAW, CA 396982 3288 4827 473 GOOGLE-CLOUD-PLATFORM, US 749 3215 54766 2466 DNIC-AS-00749, US 16625 2889 1235 2156 AKAMAI-AS, US 36352 2847 231 914 AS-COLOCROSSING, US 174 2679 8762 812 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 7287 1711 149 UNI2-AS, ES 39891 4833 298 66 ALJAWWALSTC-AS, SA 9009 4014 378 2281 M247, RO 20940 3892 3395 127 AKAMAI-ASN1, NL 12389 3160 2317 869 ROSTELECOM-AS PJSC Rostelecom. Technical 212238 2533 178 1824 CDNEXT, GB 34984 2417 363 576 TELLCOM-AS, TR 8452 1666 1852 13 TE-AS TE-AS, EG 13188 1607 100 27 TRIOLAN, UA 203020 1456 166 842 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 12504 3297 576 UNINET, MX 10620 3455 463 1098 Telmex Colombia S.A., CO 13999 2504 511 350 Mega Cable, S.A. de C.V., MX 11830 1990 369 64 Instituto Costarricense de Electricidad y 28573 1379 2435 257 Claro NXT Telecomunicacoes Ltda, BR 3816 1353 789 206 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 6147 1276 371 23 Telefonica del Peru S.A.A., PE 22884 1060 67 364 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 26615 1027 2486 56 TIM SA, BR 18881 911 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 1788 594 28 RAYA-AS, EG 36992 1679 1509 397 ETISALAT-MISR, EG 24863 1265 389 20 LINKdotNET-AS, EG 36903 1250 554 97 MT-MPLS, MA 29571 1165 100 70 ORANGE-COTE-IVOIRE, CI 37069 1085 1096 13 MOBINIL, EG 36935 998 521 44 Vodafone-, EG 20011 580 154 212 NTT-DATA-Inc, ZA 36914 554 82 3 KENET-AS, KE 15399 546 57 56 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 14312 37278 5387 AMAZON-02, US 9808 13466 8760 120 CHINAMOBILE-CN China Mobile Communication 8151 12504 3297 576 UNINET, MX 12479 7287 1711 149 UNI2-AS, ES 7545 6094 833 590 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4967 4193 77 ERX-CERNET-BKB China Education and Resear 39891 4833 298 66 ALJAWWALSTC-AS, SA 11492 4780 317 801 CABLEONE, US 22773 4640 3108 403 ASN-CXA-ALL-CCI-22773-RDC, US 9498 4518 538 315 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 13466 13346 CHINAMOBILE-CN China Mobile Communications Grou 8151 12504 11928 UNINET, MX 12479 7287 7138 UNI2-AS, ES 7545 6094 5504 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4967 4890 ERX-CERNET-BKB China Education and Research Net 39891 4833 4767 ALJAWWALSTC-AS, SA 22773 4640 4237 ASN-CXA-ALL-CCI-22773-RDC, US 9498 4518 4203 BBIL-AP BHARTI Airtel Ltd., IN 11492 4780 3979 CABLEONE, US 7552 3980 3952 VIETEL-AS-AP Viettel Group, VN 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 53775 UNALLOCATED 8.20.88.0/24 3737 AS-PTD, US 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 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.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.142.24.0/24 Origin: 62164 HEYMMAN-2, CA 23.142.24.0/24 Transit: 64236 UNREAL-SERVERS, US 23.147.240.0/24 Origin: 32302 RESERVED, ZZ 23.147.240.0/24 Transit: 32787 PROLEXIC-TECHNOLOGIES-DDOS-MITIGATION-NE 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:18 /9:14 /10:41 /11:94 /12:298 /13:579 /14:1194 /15:2091 /16:13695 /17:8275 /18:13557 /19:24938 /20:45196 /21:52509 /22:113004 /23:105082 /24:630972 /25:704 /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 6714 12504 UNINET, MX 12479 6231 7287 UNI2-AS, ES 11492 3593 4780 CABLEONE, US 39891 3521 4833 ALJAWWALSTC-AS, SA 6327 3459 3671 SHAW, CA 22773 2984 4640 ASN-CXA-ALL-CCI-22773-RDC, US 7155 2820 3861 VIASAT-SP-BACKBONE, US 16509 2451 14312 AMAZON-02, US 30036 2310 2653 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2210 3455 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:1803 2:1527 3:970 4:10 5:4875 6:188 7:6 8:1529 9:6 11:172 12:1230 13:557 14:2686 15:405 16:303 17:385 18:910 20:582 21:4 22:188 23:8057 24:2562 25:2 27:2728 29:19 31:3367 32:32 33:1 34:81 35:278 36:4507 37:4581 38:9360 39:1176 40:462 41:4363 42:953 43:2762 44:401 45:19187 46:5193 47:369 49:2148 50:2054 51:597 52:1628 54:357 55:1094 56:11 57:292 58:2207 59:1377 60:1189 61:2981 62:3101 63:1758 64:5897 65:2131 66:5895 67:3232 68:1492 69:4131 70:1042 71:628 72:3006 74:2891 75:1512 76:604 77:2779 78:1909 79:1790 80:2291 81:2132 82:3587 83:1467 84:2010 85:3581 86:1107 87:2386 88:1332 89:4515 90:831 91:8406 92:2830 93:2981 94:4156 95:4538 96:1462 97:312 98:950 99:762 100:68 101:1229 102:4175 103:32178 104:5469 105:767 106:913 107:2795 108:1207 109:4217 110:2252 111:3929 112:2763 113:1626 114:2090 115:2215 116:2111 117:3097 118:2545 119:2049 120:2369 121:1555 122:2874 123:2268 124:1690 125:2930 126:125 128:1585 129:968 130:1491 131:2229 132:780 133:461 134:1624 135:365 136:1493 137:1201 138:2847 139:1586 140:1743 141:1577 142:2219 143:2134 144:1324 145:632 146:2193 147:2119 148:2780 149:2840 150:1282 151:2650 152:2275 153:589 154:8080 155:2218 156:3249 157:2087 158:1405 159:2667 160:3663 161:2003 162:3991 163:2323 164:1952 165:2548 166:1328 167:2122 168:3808 169:783 170:5450 171:1066 172:4473 173:3433 174:907 175:1340 176:3761 177:4734 178:4299 179:2275 180:2763 181:4312 182:3801 183:2364 184:2079 185:21661 186:5383 187:4734 188:4391 189:4447 190:9700 191:1553 192:11463 193:9510 194:7836 195:5603 196:3285 197:3222 198:6220 199:6093 200:8189 201:6370 202:10701 203:10503 204:4647 205:3710 206:4403 207:3869 208:4279 209:5387 210:4946 211:2740 212:4920 213:3975 214:1040 215:54 216:7136 217:3383 218:1625 219:572 220:2200 221:1267 222:896 223:3136 End of report

2 2

Reminder to Submit Presentations for NANOG 96
by NANOG Program 10 Nov '25

10 Nov '25

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 96, taking place in San Francisco, CA on 02-04 February 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://www.nanog.org/program/call-presentations/. Requested Topics: We are aiming to spotlight presentations throughout NANOG 96 focusing on AI + Network Infrastructure. Topics can range from practical applications in daily troubleshooting to strategic discussions on future network architecture. Potential artificial intelligence topics may include deploying and scaling your network, adding machine learning to support services (like DNS, monitoring, et al.), and innovations in power and cooling needs. 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: - Network Automation - designing networks for AI traffic, different approaches for different objectives, recruiting in an AI world, benefits and drawbacks for 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-presentations/> for an extensive listing of requested topics We are looking to schedule 1,600 minutes of content between General Session and Breakout Rooms for NANOG 96, and have confirmed 150 minutes to date - so don’t wait! Presentation abstracts are welcomed now and draft slides should be submitted no later than Monday, 05 January 2026 to be considered for NANOG 96. 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: - Submitter enters abstract (and draft slides if possible) in the Program Committee Tool prior to the deadline for slide submission. - PC performs initial review and assigns a “shepherd” to help develop the submission — typically within 2 weeks. - Submitter develops draft slides of talk, if not already submitted with the initial proposal. Please submit initial draft slides early — the PC does not evaluate submissions until draft slides are available for review. NANOG Staff is available to assist with slide templates upon request from the submitter. - Panel and Track submissions should provide a topic list and intended/confirmed participants in the abstract. - PC reviews the slides and continues to work with Submitter as needed to develop the topic and content. - FINAL SUBMISSION DEADLINE Draft presentation slides should be submitted prior to the published deadline for slides (05 January 2026). - PC evaluates submissions to determine presentations for the agenda (posted on 12 January 2026). - Submitters notified. - Agenda assembled and posted. - Final presentation slides must be submitted prior to the published deadline for slides (26 January 2026 for in person + live remote presentations). 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 96 Calendar of Events Date Event/Deadline TODAY! CFP Reminder Announcement December 08, 2025 Call for Content Reminder #2 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 Final slides for accepted presentations must be submitted by Monday, 26 January 2026. Materials received after that date, and prior to 30 January may be accepted based on Shepherd availability, but is not guaranteed. Materials received after 30 January will not be accepted. We look forward to seeing you in February! Sincerely, Adair Thaxton Program Committee Chair Sent on behalf of the NANOG PC

2 1

Hardware question
by Craig Smith 10 Nov '25

10 Nov '25

Hello, Is anyone out there aware of a fail safe switch/router/1U server where upon power failure or watchdog event 2 ports would fail to pass through data, but could also be assigned an IP address and act as a bridge in "normal" mode? The desire is to have an appliance that could perform monitoring and send telemetry in between a customer device and an Internet connection but not create a single point of failure or require multiple ISP handoffs. Best, Craig

14 18

Stream All N95 Talks Now! + Board Election Results + MORE!
by Nanog News 10 Nov '25

10 Nov '25

*** Registration is Open for NANOG 96!* ------------------------------------------------------------ *Take Advantage of Early Bird Pricing! Deadline Approaching!* *Lock in the lowest rate of the season, rates increase after Sunday, November 16.* Join us in SFO Feb 2-4, 2026 for three days of networking, education, and the latest in network engineering and technology. *REGISTER NOW* (https://nanog.org/events/nanog-96/registration/registrant) *** Inside N95: Attendees Share What Made Texas Unforgettable* ------------------------------------------------------------ *Community Shares what Made N95 a Standout Conference for Learning, Connection, and Inspiration.* "A highlight of NANOG 95 in Arlington was meeting Len Bosack, co-founder of Cisco and one of the original architects of the modern Internet. We spoke about the early creation of BGP, famously drafted on a pair of napkins in 1989 to restore global connectivity during a routing crisis." *READ MORE* ( https://nanog.org/stories/inside-nanog-95-attendees-share-what-made-texas-u… ) *** Stream NANOG 95 Talks Now!* ------------------------------------------------------------ *Break out the Popcorn, All N95 Videos are Available to Watch on YouTube* Time to get inspired. Watch or rewatch the presentations that are evolving the Internet. Make sure to subscribe to the NANOG YouTube channel! *WATCH NOW* ( https://www.youtube.com/playlist?list=PLO8DR5ZGla8hP_Yyt5cz9o7xPW37eZ8A9) *** NANOG Election Results are In!* ------------------------------------------------------------ *Meet Your New Board Members* Congratulations to elected board members Leslie Daigle, John van Oppen, and Michael Costello! Thank you to all candidates for their commitment to the NANOG Organization and Network Operators’ community and all who voted. *VIEW RESULTS* ( https://nanog.org/members/elections/past-elections/2025-nanog-elections-sum… ) *** TORNOG Unnumbered ::2* *Join Us for the Fall Event, Wednesday* ------------------------------------------------------------ *You're Invited to a Community Meetup for Network Operators in Toronto* Location: 192 Spadina Ave, Toronto, ON, Canada Date/Time: Nov 12 from 5:30pm to 11pm EST *LEARN MORE* (https://tornog.ca) *** 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

2 1

Google/Youtube assistance
by Dennis Burgess - LTI Support 05 Nov '25

05 Nov '25

We have had a network that directly peers with Google, traffic goes though the peering without issues, no latency issues. However, we have periods of not being able to reach youtube.com and customers are having issues getting playback though YouTube. Starting around 5pm PST.. It’s a on/off issue, but looking for someone at YouTube/google to take a few playback ids and see what they can see. See if we can figure it out. So looking for google/YouTube person to email me off list to discuss. Dennis Burgess MikroTik Certified: Trainer | Network Associate | Routing Engineer | Wireless Engineer | Traffic Control Engineer | Inter-Networking Engineer | Security Engineer | Enterprise Wireless Engineer Hurricane Electric: IPv6 Sage Cambium Certified: ePMP Author: Learn RouterOS – Second Edition<https://shop.linktechs.net/126> Link Technologies, Inc.<http://www.linktechs.net/> – MikroTik & ISP Support Services | Shop On-Line<https://shop.linktechs.net/> 📞 Office: 314-735-0270 or 1-866-620-0074 📡 Create Wireless Coverage with www.towercoverage.com<http://www.towercoverage.com/>

1 0

CAIDA and Internet2 are working on a tool to assist network operators plan their RPKI-ROAs
by Steven Wallace 01 Nov '25

01 Nov '25

You can kick the tires here: https://rootbeer.testing.ns.internet2.edu/roa-planner/ The implementation remains fragile and will be unavailable intermittently, but we hope to improve it over the next couple of weeks. Please send me (ssw(a)internet2.edu) any suggestions, concerns, etc. From the help page: The RPKI-ROA Planner is a tool designed to help network operators efficiently plan their Route Origin Authorizations (ROAs), which are vital for securing BGP routing. To generate a comprehensive set of ROA recommendations for a user-supplied IP prefix, the Planner aggregates routing and registration information from four key sources: - Internet Routing Registry (IRR): Route Objects are gathered from services like https://stat.ripe.net/data/whois/. - Regional Internet Registries (RIRs): IP registration data is fetched from sources such as https://rdap.arin.net/registry/ip/. - Routing History: Historical routing data is analyzed using services like RIPEstat (https://stat.ripe.net/data/routing-history) - Global Route Views: The Planner includes routes observed in the global research and education community (via Routeviews). Crucially, these routes may be longer (more specific) than those typically seen in the Default-Free Zone (DFZ). Assumption: If a route was observed in the past, is currently visible, or is documented in an IRR object, it is a candidate for a new ROA. It excludes any candidate routes that are already covered by an existing, valid ROA, ensuring you only focus on what's missing. All candidate routes are presented to you in the table. You have full control to deselect individual routes or use age filters to exclude older, potentially stale data before the final ROA set is calculated. The Planner prioritizes generating multi-prefix ROAs (covering multiple routes with one authorization) over single-prefix ROAs. Using multi-prefix ROAs is the recommended best practice for maintaining cleaner, more efficient RPKI records. thanks! Steven Wallace Director - Routing Integrity Internet2 ssw(a)internet2.edu

9 9