May 2025 - NANOG - lists.nanog.org

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 09 May '25

09 May '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 10 May, 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: 982066 Prefixes after maximum aggregation (per Origin AS): 378726 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 479412 Number of IPv4 prefixes with a valid ROA: 538896 Number of IPv4 prefixes with an invalid ROA: 1362 Number of IPv4 prefixes with no ROA: 441808 Total ASes present in the Internet Routing Table: 76897 Prefixes per ASN: 12.77 Origin-only ASes present in the Internet Routing Table: 65806 Origin ASes announcing only one prefix: 26969 Transit ASes present in the Internet Routing Table: 11091 Transit-only ASes present in the Internet Routing Table: 550 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 80 Max AS path prepend of ASN ( 37447) 75 Prefixes from unregistered ASNs in the Routing Table: 987 Number of instances of unregistered ASNs: 992 Number of 32-bit ASNs allocated by the RIRs: 46388 Number of 32-bit ASNs visible in the Routing Table: 38254 Prefixes from 32-bit ASNs in the Routing Table: 202312 Number of bogon 32-bit ASNs visible in the Routing Table: 40 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 467 Number of addresses announced to Internet: 3111055488 Equivalent to 185 /8s, 110 /16s and 240 /24s Percentage of available address space announced: 84.0 Percentage of allocated address space announced: 84.0 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: 321764 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 258259 Total APNIC prefixes after maximum aggregation: 77595 APNIC Deaggregation factor: 3.33 Prefixes being announced from the APNIC address blocks: 249485 Unique aggregates announced from the APNIC address blocks: 103255 APNIC Region origin ASes present in the Internet Routing Table: 14656 APNIC Prefixes per ASN: 17.02 APNIC Region origin ASes announcing only one prefix: 4480 APNIC Region transit ASes present in the Internet Routing Table: 1966 Average APNIC Region AS path length visible: 5.5 Max APNIC Region AS path length visible: 36 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10147 Number of APNIC addresses announced to Internet: 749234432 Equivalent to 44 /8s, 168 /16s and 105 /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: 289703 Total ARIN prefixes after maximum aggregation: 130388 ARIN Deaggregation factor: 2.22 Prefixes being announced from the ARIN address blocks: 290964 Unique aggregates announced from the ARIN address blocks: 138656 ARIN Region origin ASes present in the Internet Routing Table: 19258 ARIN Prefixes per ASN: 15.11 ARIN Region origin ASes announcing only one prefix: 7035 ARIN Region transit ASes present in the Internet Routing Table: 2006 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 34 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5209 Number of ARIN addresses announced to Internet: 1353277440 Equivalent to 80 /8s, 169 /16s and 96 /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: 273869 Total RIPE prefixes after maximum aggregation: 133924 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 271636 Unique aggregates announced from the RIPE address blocks: 174312 RIPE Region origin ASes present in the Internet Routing Table: 28918 RIPE Prefixes per ASN: 9.39 RIPE Region origin ASes announcing only one prefix: 12056 RIPE Region transit ASes present in the Internet Routing Table: 4009 Average RIPE Region AS path length visible: 5.2 Max RIPE Region AS path length visible: 44 Number of RIPE region 32-bit ASNs visible in the Routing Table: 12427 Number of RIPE addresses announced to Internet: 731501952 Equivalent to 43 /8s, 153 /16s and 213 /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: 123969 Total LACNIC prefixes after maximum aggregation: 29442 LACNIC Deaggregation factor: 4.21 Prefixes being announced from the LACNIC address blocks: 120344 Unique aggregates announced from the LACNIC address blocks: 48846 LACNIC Region origin ASes present in the Internet Routing Table: 11242 LACNIC Prefixes per ASN: 10.70 LACNIC Region origin ASes announcing only one prefix: 2702 LACNIC Region transit ASes present in the Internet Routing Table: 2524 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 56 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9194 Number of LACNIC addresses announced to Internet: 171795712 Equivalent to 10 /8s, 61 /16s and 101 /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: 35279 Total AfriNIC prefixes after maximum aggregation: 6768 AfriNIC Deaggregation factor: 5.21 Prefixes being announced from the AfriNIC address blocks: 49170 Unique aggregates announced from the AfriNIC address blocks: 13955 AfriNIC Region origin ASes present in the Internet Routing Table: 1911 AfriNIC Prefixes per ASN: 25.73 AfriNIC Region origin ASes announcing only one prefix: 696 AfriNIC Region transit ASes present in the Internet Routing Table: 378 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 80 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1277 Number of AfriNIC addresses announced to Internet: 105022208 Equivalent to 6 /8s, 66 /16s and 131 /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 10803 8757 101 CHINAMOBILE-CN China Mobile Communication 7545 6161 842 653 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4773 4192 76 ERX-CERNET-BKB China Education and Resear 9498 4368 534 301 BBIL-AP BHARTI Airtel Ltd., IN 7552 3905 1332 26 VIETEL-AS-AP Viettel Group, VN 7713 3693 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3277 1869 102 VNPT-AS-VN VNPT Corp, VN 24560 2867 852 535 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2411 11524 646 KIXS-AS-KR Korea Telecom, KR 45090 2208 1439 86 TENCENT-NET-AP Shenzhen Tencent Computer 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 13300 40822 4722 AMAZON-02, US 11492 4725 313 592 CABLEONE, US 7155 3859 286 85 VIASAT-SP-BACKBONE, US 6327 3622 1320 81 SHAW, CA 174 3503 8749 891 COGENT-174, US 22773 3344 3031 166 ASN-CXA-ALL-CCI-22773-RDC, US 749 3253 54861 2504 DNIC-AS-00749, US 396982 3164 3852 416 GOOGLE-CLOUD-PLATFORM, US 16625 3019 1260 2221 AKAMAI-AS, US 36352 2777 228 852 AS-COLOCROSSING, 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 7696 1714 148 UNI2-AS, ES 39891 4797 293 62 ALJAWWALSTC-AS, SA 20940 3954 3395 127 AKAMAI-ASN1, NL 9009 3802 328 1991 M247, RO 12389 3075 2303 886 ROSTELECOM-AS PJSC Rostelecom. Technical 34984 2362 360 584 TELLCOM-AS, TR 212238 2138 151 1579 CDNEXT, GB 8452 1647 1852 14 TE-AS TE-AS, EG 13188 1606 100 34 TRIOLAN, UA 8551 1428 366 39 BEZEQ-INTERNATIONAL-AS Bezeqint Internet 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 12069 3247 582 UNINET, MX 10620 3533 486 993 Telmex Colombia S.A., CO 13999 2511 540 362 Mega Cable, S.A. de C.V., MX 11830 1995 369 64 Instituto Costarricense de Electricidad y 28573 1358 2438 262 Claro NXT Telecomunicacoes Ltda, BR 3816 1337 784 209 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 11664 1198 278 33 Techtel LMDS Comunicaciones Interactivas 6147 1191 371 22 Telefonica del Peru S.A.A., PE 22884 1051 67 376 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 6503 1042 374 163 Axtel, S.A.B. de C.V., MX 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 1744 631 30 RAYA-AS, EG 24863 1651 389 16 LINKdotNET-AS, EG 29571 1598 103 23 ORANGE-COTE-IVOIRE, CI 36992 1431 1518 283 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 36935 1036 523 45 Vodafone-, EG 20011 980 185 285 INTERNET-SOLUTIONS, ZA 37069 932 1099 15 MOBINIL, EG 36914 553 82 3 KENET-AS, KE 15399 539 57 59 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 13300 40822 4722 AMAZON-02, US 8151 12069 3247 582 UNINET, MX 9808 10803 8757 101 CHINAMOBILE-CN China Mobile Communication 12479 7696 1714 148 UNI2-AS, ES 7545 6161 842 653 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 293 62 ALJAWWALSTC-AS, SA 4538 4773 4192 76 ERX-CERNET-BKB China Education and Resear 11492 4725 313 592 CABLEONE, US 9498 4368 534 301 BBIL-AP BHARTI Airtel Ltd., IN 20940 3954 3395 127 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 8151 12069 11487 UNINET, MX 9808 10803 10702 CHINAMOBILE-CN China Mobile Communications Grou 12479 7696 7548 UNI2-AS, ES 7545 6161 5508 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 4735 ALJAWWALSTC-AS, SA 4538 4773 4697 ERX-CERNET-BKB China Education and Research Net 11492 4725 4133 CABLEONE, US 9498 4368 4067 BBIL-AP BHARTI Airtel Ltd., IN 7552 3905 3879 VIETEL-AS-AP Viettel Group, VN 20940 3954 3827 AKAMAI-ASN1, NL 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 578888 UNALLOCATED 5.59.160.0/21 57888 TELESAT-AS, HR 22542 UNALLOCATED 8.7.205.0/24 3356 LEVEL3, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-D 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 46887 CROWNCASTLE-AS46887, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 3356 LEVEL3, 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 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, 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.152.48.0/24 Origin: 46167 RESERVED, ZZ 23.152.48.0/24 Transit: 7018 ATT-INTERNET4, US 23.155.208.0/24 Origin: 396169 AS-GHCIL-01, US 23.155.208.0/24 Transit: 35985 ONERINGNET-ATL-1, 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:16 /10:41 /11:93 /12:300 /13:581 /14:1214 /15:2146 /16:13997 /17:8330 /18:13781 /19:24815 /20:44487 /21:52077 /22:112210 /23:101805 /24:605356 /25:801 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 6617 7696 UNI2-AS, ES 8151 6265 12069 UNINET, MX 11492 3533 4725 CABLEONE, US 39891 3489 4797 ALJAWWALSTC-AS, SA 6327 3417 3622 SHAW, CA 7155 2818 3859 VIASAT-SP-BACKBONE, US 22773 2496 3344 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2312 13300 AMAZON-02, US 30036 2219 2559 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2199 3533 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:1710 2:1508 3:700 4:10 5:4647 6:162 7:6 8:1609 9:1 11:172 12:1366 13:378 14:2538 15:353 16:283 17:374 18:917 20:518 21:4 22:188 23:7504 24:2752 25:2 27:2694 29:19 31:3242 32:40 33:1 34:83 35:206 36:2772 37:4644 38:9137 39:909 40:167 41:4182 42:945 43:2558 44:376 45:18606 46:5041 47:298 49:1927 50:1893 51:591 52:1556 54:306 55:1095 56:11 57:256 58:2126 59:1362 60:1164 61:2784 62:2919 63:1813 64:5459 65:2155 66:4653 67:3061 68:1123 69:3842 70:1086 71:633 72:2853 74:2778 75:1608 76:620 77:2735 78:1871 79:1757 80:2215 81:2044 82:3154 83:1432 84:1854 85:3438 86:1053 87:2404 88:1286 89:4364 90:774 91:8345 92:2713 93:2887 94:4039 95:4326 96:1419 97:316 98:980 99:675 100:72 101:1180 102:3905 103:32220 104:4826 105:753 106:1034 107:2622 108:1226 109:4088 110:2234 111:3373 112:2062 113:1526 114:1974 115:2142 116:2048 117:2613 118:2360 119:1922 120:1909 121:1424 122:2765 123:2173 124:1620 125:2876 126:91 128:1582 129:960 130:1300 131:1947 132:780 133:451 134:1531 135:331 136:1305 137:1167 138:2885 139:1627 140:1586 141:1509 142:1903 143:1718 144:1108 145:503 146:2164 147:2098 148:2644 149:2872 150:1247 151:1849 152:2086 153:497 154:8136 155:1690 156:3378 157:1896 158:1305 159:2448 160:3560 161:1881 162:3727 163:2129 164:1704 165:2202 166:1477 167:1905 168:4037 169:792 170:5070 171:1008 172:4405 173:3262 174:910 175:1299 176:3670 177:4704 178:3627 179:2274 180:2620 181:4071 182:3423 183:1845 184:2063 185:21565 186:5083 187:4468 188:4221 189:4264 190:9602 191:1492 192:11252 193:9485 194:7766 195:5525 196:3284 197:3721 198:6227 199:8506 200:8197 201:6281 202:10463 203:10547 204:4545 205:3638 206:4645 207:3571 208:4254 209:5213 210:4834 211:2637 212:4541 213:3703 214:1031 215:48 216:6709 217:3122 218:1395 219:539 220:2088 221:1077 222:847 223:2387 End of report

1 0

3 Netblocks
by info＠netstyle.io 09 May '25

09 May '25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, Years ago I was mentioned in this mailing list regarding "unauthorized use of ip netblocks". This was of course false, not 99.99% false, but 100% false. Some of the quotes that have been here: "Cohen is a theft and a crook" "Cohen sits with impunity in Israel" "Any half brain..." "I have a receipt of the Brooklin Bridge" "Cohen bribed" I hereby link to a police certificate that I received when I purchased a group of netblocks in 2018: https://limewire.com/d/vQYtW#e3cqcwR4Hz (STA-STATMENT-CHIHUAN.pdf) ASLine Limited (AS137951 & AS18013) leased from us the following 3 netblocks years ago (which are listed in the mentioned above police certificate), then ASLine Limited stopped paying us and kept using those 3 netblocks: 155.159.0.0/16 160.121.0.0/16 168.206.0.0/16 They (ASLine) ignored our emails and phone calls for a very long time. ASLine used tier1 providers that accepted BGP announcements which are related to the 3 netblocks above. Including Cogent (which persistently disconnected me but kept to provide service to ASLine). To verify it you can look at the BGP paths history (from approximately two weeks ago and before it), not the currently, because currently Cogent and other tier1 providers stopped to accept the BGP announcements which are related to above netblocks except for NTT. ASLine cannot create route objects in AFRINIC. The account of ASLine in RADb was suspended. ASLine route objects are only in NTTCOM routing registry and NTT is the only one now accepting BGP announcements which are related to the above 3 netblocks from ASLine. NTT is aware (by AFRINIC) that ASLine is not one of the two disputants that AFRINIC are referring to in their whois of the 3 netblocks. NTT is also aware that according to AFRINIC the disputants are Safren Computer Services, Mega Plastics (Pty) Ltd, The Atomic Energy Board - and Afri Holdings. NTT is claiming that they (NTT) received Letters of Authorizations dated 2024 and valid until 2025 from the other disputants (meaning: Safren Computer Services, Mega Plastics (Pty) Ltd and The Atomic Energy Board). I hereby link to it: https://limewire.com/d/vQYtW#e3cqcwR4Hz (NTT.png) I note that The Atomic Energy Board is a governmental entity in South Africa and that NTT is aware of it. I note that the new owner ASLine Limited in the following 3 emails told me that he was "assured" by the past owner that he will be able to use the 3 netblocks (including the governmental netblock) "for free", I hereby add the 3 links to those 3 emails: https://limewire.com/d/vQYtW#e3cqcwR4Hz (Email1.png) https://limewire.com/d/vQYtW#e3cqcwR4Hz (Email2.png) https://limewire.com/d/vQYtW#e3cqcwR4Hz (Email3.png) In the above link there is also an email communication from the year 2020 with the Atomic Energy Board (AtomicEnergyBoard.pdf) when they wrote that they will pass the matter to their lawyers and to the South African Authorities, they wrote that they will communicate further in this regards - it never happened. I also note that by looking at the saved BGP history of all of the netblocks in the linked police certificate, it is clear that those netblocks were used by many many Autonomous Networks which are not related to the entities that initially received them from IANA, and currently NTT have (according to their own words) a proof that the governmental entity Atomic Energy Board gave a Letter of Authorization to ASLine Limited, dated 2024, while the new owner of ASLine Limited owner (in his own words) wrote that he was "assured" that he can also use that netblock "for free" by the past seller, and when he reached out to the past seller - the past seller refused to take responsibility and claimed that they (the past owner) are not obligated, because they didn't charge anything for those 3 netblocks from the new owner. I simply ask, what is going on here? Because the issue was written in NANOG in many threads, maybe you would be interested to know too. I copy NTT, ASLine, AFRINIC and the emails of the Atomic Energy Board which I have on file. I've decided to be 100% transparent because of the severe damages that have occurred to me and that are occurring to me. Kind Regards, Elad -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsG5BAEBCgBtBYJoHeulCZCAS+uEnipSW0UUAAAAAAAcACBzYWx0QG5vdGF0 aW9ucy5vcGVucGdwanMub3JnDnJqZbzMHaH6OMlzc6Bj8tpkzghCx34ExhmV bc56s24WIQTD50Y2bI5NSOj/nnWAS+uEnipSWwAAJWEP/jiVocp44TBwv91f ZYSRpAwPcIlHCdW0cSg6JSOvM+0Z7FSixZl+LxjNDRQyYOLKirXw9bzvnBhk JSoJWodvRxnLdzeJ0sqL4vqJ8J43zMX0FgfeUgcNuv0mrqd8+xGEjylYdI10 D1oj2d0y1D1P2oIulY4luvPnxF7tz7fjIr6+9NkVH5tA+mNEY6kB53WJTkMG IRlCOW6PiJ8iQn5bJzu3k7202QxNLOV2Ry/5Tr+fntRrGdPJoeaNh8ew0mqR duRzK9Ifdx3j699v+cF2zErAmpNzemxaNI1D5D54RGjg2tGxXGmbEzSa8Cep s4jsf9FI5DYVrlSQFSEdduMgFAg2w4zxDhnGH6iDPWF2+mqWFTbj8WdQkpOf segEKcBJXcTnhenQ5fiCBItaWc7+mmhJV3/2L/54PJr1Lj0byRazljCIteKk 6lRklleoxPx6xDah3UwcDKz7G1kWr1sN1Y6HzEWJoaAmFhpGYE92hBPVo4s5 WXN/OtcJ+eWZPwwO0puXwdWpWMK68MlPDIy+1p0z7IQ2QiFoslhOSzGd1DTk tGGkeUb3UsSR7UomrnCHNJ6C1+cUqGyJSu3dNEDlkBTfb8HlZhn66kdC6F4A z50W782WEFyYANraChbaxEyn11bkRWyDGYde76TCn5KM5SVnq6RZvD6s3TwS LQebqpY6 =byLb -----END PGP SIGNATURE-----

1 0

Re: NJ/NYC Local 100GBase LR4
by John R. Levine 09 May '25

09 May '25

It appears that Kevin McCormick via NANOG <nanog(a)lists.nanog.org> said: >Try Precision Optical Technologies who was bought recently by Belden. > >They are located in Rochester, NY. > >Good prices, excellent warranty, excellent customer service, made in USA, and no issues with optics for years, unlike FS. Just FYI, Rochhester is about 5 1/2 hours from New York City, as far away from NYC as Richmond VA or Portland ME. Sounds like a fine resource, but not very convenient to NYC. R's, John

1 0

Fwd: NJ/NYC Local 100GBase LR4
by Alex Buie 09 May '25

09 May '25

Howdy y'all, I find myself onsite travelling in Weehawken and short two 100g LR4 1310 optics, and the soonest I can get them via shipping is not soon enough. Anyone know of a source who would stock 100g QSFP28 LR4 1310 optics for sale locally in NYC/EWR area or interested in selling their cold spare to me? Feel free to reply directly. Microcenter appears to unfortunately only have up to 10g optics. Thanks! A

8 10

Spoofer Report for NANOG for Apr 2025
by CAIDA Spoofer Project 08 May '25

08 May '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 Apr 2025: ASN Name Fixed-By 7922 COMCAST-7922 2025-04-02 32489 AMANAHA-NEW 2025-04-02 33490 COMCAST-33490 2025-04-09 212219 2025-04-19 10708 SELECTNET 2025-04-22 6360 UNIVHAWAII 2025-04-28 Further information for the inferred remediation is available at: https://spoofer.caida.org/remedy.php Source Address Validation issues inferred during Apr 2025: ASN Name First-Spoofed Last-Spoofed 5650 FRONTIER-FRTR 2016-02-22 2025-04-05 7029 WINDSTREAM 2016-06-21 2025-04-15 40676 AS40676 2016-08-29 2025-04-30 27364 ACS-INTERNET 2016-09-27 2025-04-23 63296 AWBROADBAND 2017-09-01 2025-04-26 21804 ACCESS-SK 2019-06-09 2025-04-28 32035 CCDT 2021-06-09 2025-04-28 12183 TALKIE-COMMUNICATIONS 2022-12-10 2025-04-30 395418 ARIN-CHA 2023-04-14 2025-04-29 400282 2023-04-27 2025-04-30 393577 SCCNET 2023-05-03 2025-04-24 61461 Airtek Solutions C.A. 2023-05-13 2025-04-07 20119 ARROW 2023-10-19 2025-04-25 394684 WISPERNET 2024-01-17 2025-04-24 3801 MISNET 2024-09-09 2025-04-25 138915 KAOPU-HK 2025-03-30 2025-04-20 273843 2025-04-02 2025-04-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

1 0

Team Up with Meta Engineers for N94 Hackathon! N94 Speaker Highlight, Channel Your Inner Camper + More!
by Nanog News 08 May '25

08 May '25

*** Team Up with Meta Engineers for N94 Hackathon!* ------------------------------------------------------------ *Ready to Build, Break, + Brainstorm with the Best?* Whether you're a first-timer or a seasoned hacker, come collaborate on real-world networking problems, sharpen your skills, and connect with the community. June 8-11 | In-person only. *Please note that you MUST be registered for N94 to register/attend the Hackathon.* *LEARN MORE* (https://nanog.org/events/nanog-94-hackathon/) *** NANOG 94 Speaker Highlight* ------------------------------------------------------------ *Q&A: Kang Xi of Meta on Automating Network Provisioning at Scale* In his upcoming talk, “Automate to Dominate: Supercharge Network Provisioning at Meta,” Kang will reveal how Meta is transforming network provisioning through automation, at a scale few others operate. We connected with Kang to dig into the technical strategy, the lessons learned, and the human perspective behind building and operating one of the world’s most complex networks. READ NOW (https://nanog.org/stories/articles/nanog-94-speaker-highlight/) *** Channel Your Inner Camper at our Next Women in Tech Mixer!* ------------------------------------------------------------ *Join Us the Sunday BEFORE N94 in Denver (June 9-11)* We're bringing back summer camp, at CAMP NANOGWIT with nostalgic fun: arts & crafts, storytelling, + trailblazing connections. Kick off NANOG 94 with joy, creativity, and community. Don't miss it! *LEARN MORE* (https://nanog.org/events/nanog-94/socials/) https://nanog.org/events/nanog-94/ *** N94 Hotel Block is SOLD OUT!* ------------------------------------------------------------ *Still Need a Place to Stay? No Worries, We've Got You Covered!* Overflow accommodations are now available. Check out "venue info" on the N94 homepage. *VIEW NOW* (https://nanog.org/events/nanog-94/) *** Don’t let this Opportunity Sprint Past you!* ------------------------------------------------------------ The race is on to secure your spot as a NANOG sponsor—where your brand meets the brightest minds in networking. With visibility in front of top engineers + innovators, this is your moment to lead the pack. 📣 Sponsorships are limited and going fast. 📍 Act now to lock in for NANOG 94 + beyond. Contact Shawn Winstead—swinstead(a)nanog.org for more info. *** 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

Youtube Contact?
by Evan S. Weiner 08 May '25

08 May '25

Reaching out to the group - we're trying to find a contact at Youtube to help with a content delivery issue. Google NOC has been useless for the past 7 months. If anyone knows someone or wants to throw their hand up, please reach out. Thanks, Evan [cid:8248a15a-6cb2-4230-b316-2a96e13696c0] 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/>

1 0

Re: 202505061814.AYC Re: 202505060938.AYC Re: IPv4 Leases
by Tom Beecher 07 May '25

07 May '25

Abraham- EZIP is a proposal. It could not be used operationally today for a multitude of reasons that those of us who actually do this stuff have tried to point out to you, but you continue to hand wave and ignore. There are lots of people who read this list and may be confused by your writings and think EZIP is a functional solution they could use today. This is, frankly, kinda of a dick move. EZIP is nothing more than the idea you have written down in your draft, and that in 9 years since you first proposed it, nobody has really cared about. ( https://mailarchive.ietf.org/arch/search/?q=%22draft-chen-ati-adaptive-ipv4… ) On Tue, May 6, 2025 at 11:14 PM Abraham Y. Chen <aychen(a)avinta.com> wrote: > Hi, Tom: > > 0) Thank you for your input. > > 1) You are very accurate in reciting the facts and events. However, I > am afraid that your conclusions might be flawed, because you probably > overlooked a couple subtle aspects behind the EzIP proposal: > > A. The primary purpose of the EzIP is to expand the size capacity > of the CG-NAT, nothing more. Besides activating the long-reserved 240/4 to > be used like 100.64/10 which has been proven not too challenging, there is > no other technical hurdle. As you may recall, CG-NAT was deployed over > quarter century ago despite the objections from IETF, anyway. > > B. EzIP will form an "Overlay Network" that can practically be > detached from the current Internet, while the two can work together as long > as the interface between them conforms with the established protocols. > Then, what happens within the EzIP can not be influenced from the outside. > This is nothing new, either. There were precedents in the past, such as the > Internet was deployed over PSTN with the dial-up modem serving as one of > the umbilical cords between the two. The IPv6 was built on top of of the > IPv4. Of course, the former was a big success story, while the latter is > still a WIP. > > C. There are much more than a handful devices that can support the > EzIP operation. Please have a look at Reference group E. on page 17 of the > below whitepaper: > > https://avinta.com/gallery/DeterministicInternet-SPKR.pdf > > D. In addition, IPv4 Unicast Extension Project has been working on > networking devices that support 240/4: > > > https://datatracker.ietf.org/doc/html/draft-schoen-intarea-unicast-240-08 > > Note that the products cited in the last two points are efforts by > many other groups. We just pool them together to be EzIP building blocks. > > Hope the above clears the air. > > Regards, > > > Abe (2025-05-06 23:14 EDT) > > > > On 2025-05-06 12:17, Tom Beecher wrote: > > Suriya- > > Just so it is clear, the technology that Abraham is referencing ( EZIP ) > is ONLY a proposal that has been made. It has not been accepted by any > standards body. It is not implemented or supported by any major router > vendor. It will not work for you. > > > On Tue, May 6, 2025 at 11:41 AM Abraham Y. Chen via NANOG < > nanog(a)lists.nanog.org> wrote: > >> Hi, Suriya: >> >> 0) I am glad that you requested off-list follow-ups, because what I >> am going to share is quite controversial. With a general distribution >> list, a discussion can easily be pulled off the track by personal / >> emotional opinions or business interests, as you might have noticed on >> the NANOG Forum in the past. >> >> 1) I would recommend you to consider replacing 100.64/10 netblock >> with 240/4 netblock for the CG-NAT configuration. This will reduce your >> need for IPv4 addresses by 64 fold, thus mitigating the IPv4 address >> shortage that you are facing. >> >> 2) Although there have been (and still are) various attempts to make >> use of the 240/4 netblock, none has approached it in a universal sense >> as our proposal, called EzIP (phonetic for Easy IPv4). Others are either >> piecemeal solutions for special cases or limited scope applications. >> They will fragment the Internet and lead to chaos. Characterized by >> Vint Cerf as an "Overlay Network", EzIP scheme forms a new layer of >> communication infrastructure that is independent of, yet in arm's-length >> with the current Internet core. So that, EzIP can retain the desired >> properties of the existing Internet, while shaking off the handicaps. >> The former maintains the operation characteristics as CG-NAT to avoid >> perturbing users, while the latter enables the Internet revamping into a >> new era. This far-reaching implication is possible because EzIP resolves >> the most fundamental issue of user identification resources. From such, >> many constraints are either relaxed or simply removed. >> >> 3) For a general introduction, please have a look at the below pair >> of documents. >> >> https://avinta.com/gallery/DeterministicInternetIntro-US.pdf >> >> https://avinta.com/gallery/DeterministicInternet-SPKR.pdf >> >> 4) Since this topic touches many aspects of the Internet and we are >> not an operatorbut just a system analyst, we likely have not covered >> many aspects that hands-on parties like you are familiar with. Please >> browse through our website to see other background information which may >> be relevant, then let us know your concerns. So that we can evaluate >> them for you. >> >> Regards, >> >> >> Abe (2025-05-06 11:40 EDT) >> VP Engineering >> Avinta Communications, Inc. >> Milpitas, CA 95035 USA >> O: +1(408)942-1485x66 >> M: +1(650)248-1829 >> Teams: Abraham.Y.Chen >> eMail: AYChen(a)Avinta.com >> WebSite: www.Avinta.com >> >> >> On 2025-05-06 04:36, Suriya Kamon via NANOG wrote: >> > Hi NANOG, >> > >> > We are running short of IPv4 addresses. >> > >> > We are a small ISP and longer prefixes are okay with us (even /24s). >> > >> > Please contact me off-list. >> > >> > (Proper ROA coverage is a must). >> > >> > Thanks. >> > >> > Best Regards, >> > Suriya >> > _______________________________________________ >> > NANOG mailing list >> > >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/3MYN3WE… >> >> >> >> -- >> This email has been checked for viruses by Avast antivirus software. >> www.avast.com >> _______________________________________________ >> NANOG mailing list >> >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/LTKZLWU… > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_4161442180352669907_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >

1 0

IPv4 Leases
by Suriya Kamon 06 May '25

06 May '25

Hi NANOG, We are running short of IPv4 addresses. We are a small ISP and longer prefixes are okay with us (even /24s). Please contact me off-list. (Proper ROA coverage is a must). Thanks. Best Regards, Suriya

8 9

Re: outages list badly broken, flooding messages
by Josh Luthman 05 May '25

05 May '25

What's being migrated if not the subscription database? On Mon, May 5, 2025, 1:16 AM virendra rode <virendra.rode(a)gmail.com> wrote: > It is a new instance. I’m referring to the migration task from PUCK to PCH > in order to minimize the pain > > — > regards, > /vrode > > On May 4, 2025, at 17:10, Josh Luthman <josh(a)imaginenetworksllc.com> > wrote: > > > If it requires everyone to resubscribe why don't we just start up a whole > new instance? > > On Sun, May 4, 2025, 8:01 PM virendra rode via NANOG < > nanog(a)lists.nanog.org> wrote: > >> Testing is currently in progress, and as the newly implemented >> mailman3, I'm adapting to the system and retrieving data from the >> archives in preparation for go live on PCH infra. It's important to >> note that we may require the community to re-subscribe, we are still >> trying to determine that. >> >> More updates will be provided soon. >> >> >> /vrode >> >> >> On Sat, 2025-05-03 at 23:18 -0500, Andy Ringsmuth via NANOG wrote: >> > >> > >> > > On Apr 27, 2025, at 5:48 PM, Jared Mauch via NANOG >> > > <nanog(a)lists.nanog.org> wrote: >> > > >> > > On Sun, Apr 27, 2025 at 02:03:23PM -0500, Mike Hammett via NANOG >> > > wrote: >> > > > Meaning fixing Puck or the divorce of Outages from Puck? >> > > >> > > >> > > I'm working on fixing puck, there's a long backstory of what >> > > transpired here which resulted in having to revert to a backup from >> > > 2023 >> > > due to some issues related to a series of events that made it far >> > > easier >> > > to just revert to a backup than attempt to restore the stuation. >> > > >> > > Most things should be back now but the state of mailman in the >> > > modern universe is an ongoing problem. It depended on python2 and >> > > was >> > > never updated to support python3. >> > > >> > > Migrating to mailman3 is also a very large task, so in the midst >> > > of all the restoration efforts that had to be undertaken this was a >> > > lower priority item. >> > > >> > > It's extremely hard when you are carrying around nearly 30 years >> > > of legacy as well. >> > > >> > > Either way I expect it all to be resolved in the next ~24 hours >> > > or less one way or another. >> > > >> > > - Jared >> > > _______________________________________________ >> > >> > How goes the transition? Any help/resources/etc. needed? Or are >> > things all sorted out and working? >> > >> > >> > -Andy >> > _______________________________________________ >> > NANOG mailing list >> > >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/6I7B4KU… >> >> _______________________________________________ >> NANOG mailing list >> >> https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/F2COSML… > >

1 0