- NANOG - lists.nanog.org

rpki roa irr - i now believe
by Aaron Gould 18 May '25

18 May '25

ok ok, now I understand and am a believer! some of our address space was hijacked. i did the arin.net roa entries, and BAM-O... moments later, all my routes are validated and the erroneous hijacked routes are gone! love it wanted to share and emphasize to others, if you don't have your prefixes protected at your RIR (ARIN), do it. it only takes a few minutes. https://www.arin.net/resources/manage/rpki/roa_request/ https://youtu.be/cVftieOVn1M -- -Aaron

8 14

Someone from AWS/Amazon US Peering, get in touch please?
by Dan Mahoney 17 May '25

17 May '25

(Apologies to other list denizens) Hey there Amazon Peering, Dayjob (F-Root) have a pending peering session with you, and you’ve sent us a note into our ticket system: "[Order Reference: 9xzknz] Reminder:Pending peering request between Amazon and AS33080" (several times), from a noreply@ mail address. We try to set up the peering session (at telx atlanta) and get nothing back from you, not even a TCP Reset, but the peer (v4 and v6) is pingable. (Note: the sessions with your ./:251 routers are up okay, but both your ./:95 sessions are acting like this). Your note says to refer to https://peering.aws if we need to contact you, but on that page you list peering-amer(a)amazon.com, which we’ve mailed with no response. The peering portal you tell us to use at https://interconnect.amazon <https://interconnect.amazon/> (these corporate-vanity tld's are annoying, especially when you feel the need to use multiple), redirects me to peeringDB to log in, and then gives me: "Read timed out" (on a gray screen). Or: "custom:custom:networks: String attributes cannot have a length of more than 2048. “ We operate multiple ASes, and my peeringDB account also is tied to multiple orgs (including my own personal one), so that may be the cause of the errors? And I suspect whatever causes that error is also causing a filtering issue. Either way, Automation is cool and all, but in this case, I think just pointing peering@ at a human who could say “I see the problem, fixed!” would have caused less headache than this. Get in touch, Please and thanks! -Dan (noc at isc org, peering at isc org)

4 4

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

16 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 17 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: 984171 Prefixes after maximum aggregation (per Origin AS): 379546 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 479725 Number of IPv4 prefixes with a valid ROA: 540162 Number of IPv4 prefixes with an invalid ROA: 1320 Number of IPv4 prefixes with no ROA: 442689 Total ASes present in the Internet Routing Table: 76906 Prefixes per ASN: 12.80 Origin-only ASes present in the Internet Routing Table: 65830 Origin ASes announcing only one prefix: 26957 Transit ASes present in the Internet Routing Table: 11076 Transit-only ASes present in the Internet Routing Table: 554 Average AS path length visible in the Internet Routing Table: 5.2 Max AS path length visible: 156 Max AS path prepend of ASN (153737) 150 Prefixes from unregistered ASNs in the Routing Table: 996 Number of instances of unregistered ASNs: 1007 Number of 32-bit ASNs allocated by the RIRs: 46439 Number of 32-bit ASNs visible in the Routing Table: 38270 Prefixes from 32-bit ASNs in the Routing Table: 203102 Number of bogon 32-bit ASNs visible in the Routing Table: 41 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 467 Number of addresses announced to Internet: 3109587584 Equivalent to 185 /8s, 88 /16s and 138 /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: 322007 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 258563 Total APNIC prefixes after maximum aggregation: 77706 APNIC Deaggregation factor: 3.33 Prefixes being announced from the APNIC address blocks: 249835 Unique aggregates announced from the APNIC address blocks: 103180 APNIC Region origin ASes present in the Internet Routing Table: 14648 APNIC Prefixes per ASN: 17.06 APNIC Region origin ASes announcing only one prefix: 4460 APNIC Region transit ASes present in the Internet Routing Table: 1953 Average APNIC Region AS path length visible: 5.4 Max APNIC Region AS path length visible: 156 Number of APNIC region 32-bit ASNs visible in the Routing Table: 10138 Number of APNIC addresses announced to Internet: 749286144 Equivalent to 44 /8s, 169 /16s and 51 /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: 290311 Total ARIN prefixes after maximum aggregation: 130879 ARIN Deaggregation factor: 2.22 Prefixes being announced from the ARIN address blocks: 291540 Unique aggregates announced from the ARIN address blocks: 138855 ARIN Region origin ASes present in the Internet Routing Table: 19252 ARIN Prefixes per ASN: 15.14 ARIN Region origin ASes announcing only one prefix: 7034 ARIN Region transit ASes present in the Internet Routing Table: 2008 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: 5214 Number of ARIN addresses announced to Internet: 1352218112 Equivalent to 80 /8s, 153 /16s and 54 /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: 273874 Total RIPE prefixes after maximum aggregation: 134012 RIPE Deaggregation factor: 2.04 Prefixes being announced from the RIPE address blocks: 271875 Unique aggregates announced from the RIPE address blocks: 174522 RIPE Region origin ASes present in the Internet Routing Table: 28925 RIPE Prefixes per ASN: 9.40 RIPE Region origin ASes announcing only one prefix: 12078 RIPE Region transit ASes present in the Internet Routing Table: 4005 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: 12444 Number of RIPE addresses announced to Internet: 731008128 Equivalent to 43 /8s, 146 /16s and 76 /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: 124897 Total LACNIC prefixes after maximum aggregation: 29520 LACNIC Deaggregation factor: 4.23 Prefixes being announced from the LACNIC address blocks: 120513 Unique aggregates announced from the LACNIC address blocks: 48848 LACNIC Region origin ASes present in the Internet Routing Table: 11250 LACNIC Prefixes per ASN: 10.71 LACNIC Region origin ASes announcing only one prefix: 2692 LACNIC Region transit ASes present in the Internet Routing Table: 2536 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: 9199 Number of LACNIC addresses announced to Internet: 171760896 Equivalent to 10 /8s, 60 /16s and 221 /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: 35530 Total AfriNIC prefixes after maximum aggregation: 6807 AfriNIC Deaggregation factor: 5.22 Prefixes being announced from the AfriNIC address blocks: 49941 Unique aggregates announced from the AfriNIC address blocks: 13922 AfriNIC Region origin ASes present in the Internet Routing Table: 1909 AfriNIC Prefixes per ASN: 26.16 AfriNIC Region origin ASes announcing only one prefix: 693 AfriNIC Region transit ASes present in the Internet Routing Table: 375 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: 1275 Number of AfriNIC addresses announced to Internet: 105096192 Equivalent to 6 /8s, 67 /16s and 164 /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 10997 8757 101 CHINAMOBILE-CN China Mobile Communication 7545 6163 842 652 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4784 4192 76 ERX-CERNET-BKB China Education and Resear 9498 4379 534 303 BBIL-AP BHARTI Airtel Ltd., IN 7552 3904 1332 26 VIETEL-AS-AP Viettel Group, VN 7713 3695 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3275 1869 102 VNPT-AS-VN VNPT Corp, VN 24560 2866 852 548 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2372 11522 628 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 13382 40824 5011 AMAZON-02, US 11492 4727 313 592 CABLEONE, US 7155 3864 286 85 VIASAT-SP-BACKBONE, US 6327 3622 1320 81 SHAW, CA 174 3374 8746 877 COGENT-174, US 22773 3349 3032 168 ASN-CXA-ALL-CCI-22773-RDC, US 749 3243 54815 2494 DNIC-AS-00749, US 396982 3165 3851 417 GOOGLE-CLOUD-PLATFORM, US 16625 3034 1264 2227 AKAMAI-AS, US 36352 2791 228 853 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 7697 1714 148 UNI2-AS, ES 39891 4797 293 62 ALJAWWALSTC-AS, SA 20940 3965 3395 127 AKAMAI-ASN1, NL 9009 3769 325 1955 M247, RO 12389 3075 2305 887 ROSTELECOM-AS PJSC Rostelecom. Technical 34984 2391 360 581 TELLCOM-AS, TR 212238 2140 150 1575 CDNEXT, GB 13188 1606 100 34 TRIOLAN, UA 8452 1585 1852 14 TE-AS TE-AS, EG 8551 1422 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 12109 3247 583 UNINET, MX 10620 3500 480 1019 Telmex Colombia S.A., CO 13999 2519 540 364 Mega Cable, S.A. de C.V., MX 11830 1996 369 64 Instituto Costarricense de Electricidad y 28573 1358 2438 262 Claro NXT Telecomunicacoes Ltda, BR 3816 1338 785 210 COLOMBIA TELECOMUNICACIONES S.A. ESP BIC, 11664 1204 278 33 Techtel LMDS Comunicaciones Interactivas 6147 1195 371 22 Telefonica del Peru S.A.A., PE 22884 1059 67 378 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 262287 1048 83 226 Latitude.sh LTDA, 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 1778 632 28 RAYA-AS, EG 24863 1653 389 16 LINKdotNET-AS, EG 29571 1598 102 33 ORANGE-COTE-IVOIRE, CI 36992 1432 1519 280 ETISALAT-MISR, EG 36903 1250 554 97 MT-MPLS, MA 37069 1107 1100 18 MOBINIL, EG 36935 1040 523 45 Vodafone-, EG 20011 980 185 285 INTERNET-SOLUTIONS, ZA 36914 550 82 3 KENET-AS, KE 15399 541 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 13382 40824 5011 AMAZON-02, US 8151 12109 3247 583 UNINET, MX 9808 10997 8757 101 CHINAMOBILE-CN China Mobile Communication 12479 7697 1714 148 UNI2-AS, ES 7545 6163 842 652 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 293 62 ALJAWWALSTC-AS, SA 4538 4784 4192 76 ERX-CERNET-BKB China Education and Resear 11492 4727 313 592 CABLEONE, US 9498 4379 534 303 BBIL-AP BHARTI Airtel Ltd., IN 20940 3965 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 12109 11526 UNINET, MX 9808 10997 10896 CHINAMOBILE-CN China Mobile Communications Grou 12479 7697 7549 UNI2-AS, ES 7545 6163 5511 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4797 4735 ALJAWWALSTC-AS, SA 4538 4784 4708 ERX-CERNET-BKB China Education and Research Net 11492 4727 4135 CABLEONE, US 9498 4379 4076 BBIL-AP BHARTI Airtel Ltd., IN 7552 3904 3878 VIETEL-AS-AP Viettel Group, VN 20940 3965 3838 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 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 46639 UNALLOCATED 8.38.73.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.147.240.0/24 Origin: 32302 RESERVED, ZZ 23.147.240.0/24 Transit: 32787 PROLEXIC-TECHNOLOGIES-DDOS-MITIGATION-NE 23.152.48.0/24 Origin: 46167 RESERVED, ZZ 23.152.48.0/24 Transit: 7018 ATT-INTERNET4, 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:92 /12:299 /13:580 /14:1213 /15:2145 /16:13988 /17:8331 /18:13773 /19:24830 /20:44699 /21:52107 /22:112211 /23:102045 /24:606987 /25:798 /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 6613 7697 UNI2-AS, ES 8151 6304 12109 UNINET, MX 11492 3533 4727 CABLEONE, US 39891 3489 4797 ALJAWWALSTC-AS, SA 6327 3417 3622 SHAW, CA 7155 2823 3864 VIASAT-SP-BACKBONE, US 22773 2499 3349 ASN-CXA-ALL-CCI-22773-RDC, US 16509 2329 13382 AMAZON-02, US 30036 2227 2567 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2186 3500 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:1711 2:1512 3:743 4:11 5:4652 6:163 7:6 8:1608 9:1 11:172 12:1366 13:417 14:2556 15:353 16:284 17:374 18:914 20:518 21:4 22:188 23:7538 24:2744 25:2 27:2693 29:19 31:3258 32:39 33:1 34:83 35:205 36:2907 37:4648 38:9140 39:910 40:169 41:4217 42:927 43:2561 44:383 45:18591 46:5049 47:303 49:1932 50:1894 51:591 52:1553 54:312 55:1089 56:11 57:257 58:2136 59:1362 60:1167 61:2791 62:2924 63:1816 64:5464 65:2171 66:4654 67:3063 68:1122 69:3845 70:1067 71:627 72:2825 74:2781 75:1612 76:620 77:2703 78:1878 79:1757 80:2215 81:2065 82:3117 83:1430 84:1865 85:3422 86:1071 87:2406 88:1290 89:4369 90:775 91:8345 92:2692 93:2895 94:4057 95:4298 96:1419 97:316 98:980 99:686 100:72 101:1176 102:3903 103:32237 104:5035 105:761 106:1034 107:2645 108:1227 109:4081 110:2242 111:3336 112:2075 113:1530 114:1975 115:2113 116:2051 117:2587 118:2347 119:1925 120:1940 121:1426 122:2768 123:2170 124:1621 125:2879 126:91 128:1597 129:965 130:1299 131:1968 132:784 133:451 134:1535 135:332 136:1342 137:1167 138:2894 139:1591 140:1597 141:1503 142:1902 143:1751 144:1115 145:506 146:2169 147:2106 148:2700 149:2863 150:1215 151:1902 152:2090 153:497 154:8042 155:1965 156:3337 157:1887 158:1311 159:2452 160:3823 161:1877 162:3740 163:2142 164:1700 165:2199 166:1485 167:1905 168:4279 169:792 170:5103 171:1007 172:4457 173:3287 174:917 175:1300 176:3699 177:4731 178:3623 179:2296 180:2622 181:4073 182:3430 183:1882 184:2067 185:21549 186:5128 187:4456 188:4248 189:4274 190:9544 191:1489 192:11254 193:9484 194:7777 195:5534 196:3280 197:3667 198:6203 199:8504 200:8222 201:6346 202:10480 203:10537 204:4557 205:3640 206:4513 207:3588 208:4261 209:5212 210:4838 211:2644 212:4545 213:3728 214:1029 215:48 216:6708 217:3131 218:1396 219:545 220:2092 221:1084 222:849 223:2408 End of report

1 0

Spectrum & GRE
by Christopher Aloi 15 May '25

15 May '25

Hey All, Hoping someone can lend a hand here. I have ~ 1k customers running GRE tunnels back to me for VoIP. Over the last three weeks these tunnels have started to break at a rate of 3-5 per day. We've narrowed it down to customers using specific Spectrum routers (rac2v1s and rac2v2s). I am still able to access the public IP but the tunnel drops and will not come back up. The fix has been to reconfigure as VPN or have the CPE router replaced with a rac2v1k. I have been unable to get anyone to listen to me at Spectrum as these accounts are owned by the customer and I can't prove a systemic issue. I have a list of accounts that have been impacted. Has anyone else encountered this? Any contacts at Spectrum that might listen to me? I am fearing all of these tunnels will go down at some point. Thanks, Chris

6 8

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

15 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-----

2 1

** NANOG 94 Denver Agenda is LIVE! + MORE!
by Nanog News 15 May '25

15 May '25

*** NANOG 94 Denver Agenda is LIVE!* ------------------------------------------------------------ *View Full Abstract and Speaker Info Now!* Attending one of our workshops at N94? Be sure to follow the additional sign up link from the agenda. *VIEW NOW *(https://nanog.org/events/nanog-94/agenda/) *** Sync Your Calendars for N94 Social Events* ------------------------------------------------------------ *Don't Miss the NANOG Social, Beer N' Gear, WIT Mixer, + More!* NANOG Socials are YOUR opportunity to get to know your peers in the industry + foster important relationships in a relaxed, casual environment. *MORE INFO* (https://nanog.org/events/nanog-94/socials/) *** Don't Miss Teaming Up w/ Meta engineers at Hackathon* ------------------------------------------------------------ *Join Us at NANOG 94 in Denver* Theme: Put Your Sleuthing Skills to the Test! The N94 Hackathon will focus on Problem-Solving/Troubleshooting Competitions created by Meta and the NANOG Hackathon Committee. Sunday, June 8 — Intro/Infrastructure Tutorial/Team Formation Monday - Tuesday, June 9-10 — Competition *LEARN MORE* (https://nanog.org/events/nanog-94-hackathon/) *** 📽️ Video of the Week—NANOG 93 Recap* ------------------------------------------------------------ *Experience the Best of Our Last Conference – In Minutes!* We produce a recap video capturing the highlights from each conference. Get inspired for N94 by watching the best moments from our last conference in Atlanta. Whether you’re a longtime attendee or a curious first-timer, this is your chance to hear from attendees and see why NANOG conferences are not to be missed! *WATCH NOW* ( https://www.youtube.com/watch?v=xXcrzK9RKtw&list=PLO8DR5ZGla8jiR9Jcl6CfeCti… ) *** 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

Many thanks to Jared Mauch
by virendra rode 14 May '25

14 May '25

I would like to extend a heartfelt thanks to Jared Mauch in keeping outages list running. His reliability and expertise played a huge role in making sure everything stayed stable all these years. We know how much goes on behind the scenes to keep systems running smoothly, and we truly appreciate your efforts. Thanks again for your dedication. With gratitude, /vrode

4 3

Re: Re: Spectrum & GRE
by The Multach's 14 May '25

14 May '25

I wonder if this has anything to do with the handling of GRE for tunneling hotspot Wi-Fi traffic from their routers. It wouldn't be the first time an ISP's handling of their own traffic caused problems with a user's traffic, even though it shouldn't. On 5/13/2025 7:00 PM, nanog-request(a)lists.nanog.org wrote: > Message: 1 > Date: Mon, 12 May 2025 16:14:15 -0400 > From: Christopher Aloi<ctaloi(a)gmail.com> > Subject: Re: Spectrum & GRE > To: North American Network Operators Group<nanog(a)lists.nanog.org> > Message-ID: > <CAMCCzApYOeUpEd7P8mjDbVKm6Nzx=0Lva4iuVhD1S+y-87Q2xw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Thanks Eric and Brendan. Yes, this is specifically related to when we put > the rac2v1s in bridge mode and I bind one of the static public IP addresses > to my router. If I captured packets on my router I can see GRE packets > leaving my router destined for my data center, but I never see any of the > return packets I send. They are being lost/dropped on the way back in. I > am up to 30 of these now. What I can't grock is why they come in at a rate > of ~5 every morning. If anyone has any contacts at Spectrum that might > listen, or a workaround, please let me know!

1 0

ARIN Consultation: Hierarchical AS-SET Names
by James Bensley 14 May '25

14 May '25

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, I raised a request with ARIN to enforce the use of hierarchical AS-SET names in the ARIN DB moving forward, as is the case in RIPE, APNIC, and LACNIC. ARIN have opened a consultation process, which closes on the 23rd of May. If you would like to see ARIN also adopt the requirement for newly created AS-SETs to have hierarchical names, please visit the following page and contact ARIN to record your support for this request: https://www.arin.net/participate/community/acsp/consultations/2025/2025-1/ With kind regards, James. -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsG5BAEBCgBtBYJoJEmnCZCoEx+igX+A+0UUAAAAAAAcACBzYWx0QG5vdGF0 aW9ucy5vcGVucGdwanMub3JnVr0rmLS4qvSLMtY2CBRvsqBwDgmlr/3T+wYR 5vCgJC0WIQQ+k2NZBObfK8Tl7sKoEx+igX+A+wAAlAcP/3rM+XfpLxIm2iFw LfdKSMqSsRVll+1lUwvGzIGB6YoNvbwfenGURA7uYrsU5rMnYPNGM51grY2d xhKeXMcS55R1FDAM1k365n05cu1g7tezsXYeS/MEvjnbA+HrEZv2xkWq+K9b ChlaXzitweTaF8cF/HgPKMukWZigIbS9yb6TgjBMv20Nr+/3tAG8VtEL9FxE 9Wu601HlN4iNYBS79pOJlDEoU3QE1xZx3UDAjsRTwNebzknu6Ilh4wRSKdMc CLd9BpXScJQFnzjDCE3P4ldRk8GK3LbdtxX6aHGcdmcMPDTdJJPzn1Xp6NDY rx3KzeBsv6UOyiqxqtNr0riiSSv3o6/NkYaN52vjgjcrNulhbmijystE7t1P w1+aN/sOGHHf+X+Y/KR7b4eqW9K/HHNsTRY0ZFfNrYio3oRNhfv2Kl1stY7w XG4PUigTiifO4aNhzvYo+gQw+rylIKlG/JI8wMcHdirpk0dPe4r2Dv3cQgBs PZ+wcm9Q1scDKjIYzFn7sVoNluPiV1J7epyUTdmEwvkp2YFD3YLggnl/9c9F IrMhOAXO6p6ro2xZjb68b04aiRCvRIhRn43FyuOXbA/BBy+alu7VvTsdIJrt AC4PmudMYdeNFeD+fx30ra6GjQhAfDhx9rVxfty1wYeqnEnVPJalbwbpqDC2 iR0Z8Fb5 =f2NW -----END PGP SIGNATURE-----

3 2

Re: outages list badly broken, flooding messages
by virendra rode 13 May '25

13 May '25

Just a quick update: We’ve successfully addressed all the initial challenges and are excited to announce that we will go live this week! As this is a brand new installation, we would require users to sign up for an account to list. Update to follow. We sincerely appreciate your patience and trust, /vrode On Sun, 2025-05-04 at 22:16 -0700, virendra rode 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…

2 1