- Test - lists.nanog.org

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

20 Jan '23

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 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 21 Jan, 2023 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 919460 Prefixes after maximum aggregation (per Origin AS): 347315 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 444984 Total ASes present in the Internet Routing Table: 74112 Prefixes per ASN: 12.41 Origin-only ASes present in the Internet Routing Table: 63597 Origin ASes announcing only one prefix: 26170 Transit ASes present in the Internet Routing Table: 10515 Transit-only ASes present in the Internet Routing Table: 430 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 953 Number of instances of unregistered ASNs: 962 Number of 32-bit ASNs allocated by the RIRs: 41079 Number of 32-bit ASNs visible in the Routing Table: 34073 Prefixes from 32-bit ASNs in the Routing Table: 166405 Number of bogon 32-bit ASNs visible in the Routing Table: 29 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 502 Number of addresses announced to Internet: 3063801088 Equivalent to 182 /8s, 157 /16s and 229 /24s Percentage of available address space announced: 82.8 Percentage of allocated address space announced: 82.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: 312168 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 240538 Total APNIC prefixes after maximum aggregation: 68701 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 235601 Unique aggregates announced from the APNIC address blocks: 97720 APNIC Region origin ASes present in the Internet Routing Table: 13254 APNIC Prefixes per ASN: 17.78 APNIC Region origin ASes announcing only one prefix: 3844 APNIC Region transit ASes present in the Internet Routing Table: 1775 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8514 Number of APNIC addresses announced to Internet: 773715072 Equivalent to 46 /8s, 29 /16s and 244 /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-151865 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: 267202 Total ARIN prefixes after maximum aggregation: 121273 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 269209 Unique aggregates announced from the ARIN address blocks: 129792 ARIN Region origin ASes present in the Internet Routing Table: 19076 ARIN Prefixes per ASN: 14.11 ARIN Region origin ASes announcing only one prefix: 6986 ARIN Region transit ASes present in the Internet Routing Table: 1962 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4732 Number of ARIN addresses announced to Internet: 1286338048 Equivalent to 76 /8s, 171 /16s and 246 /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-401308 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, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/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: 264243 Total RIPE prefixes after maximum aggregation: 122408 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 260620 Unique aggregates announced from the RIPE address blocks: 156066 RIPE Region origin ASes present in the Internet Routing Table: 28257 RIPE Prefixes per ASN: 9.22 RIPE Region origin ASes announcing only one prefix: 12065 RIPE Region transit ASes present in the Internet Routing Table: 3969 Average RIPE Region AS path length visible: 4.2 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11001 Number of RIPE addresses announced to Internet: 719149696 Equivalent to 42 /8s, 221 /16s and 90 /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-213403 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/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: 117563 Total LACNIC prefixes after maximum aggregation: 28462 LACNIC Deaggregation factor: 4.13 Prefixes being announced from the LACNIC address blocks: 116740 Unique aggregates announced from the LACNIC address blocks: 48999 LACNIC Region origin ASes present in the Internet Routing Table: 11002 LACNIC Prefixes per ASN: 10.61 LACNIC Region origin ASes announcing only one prefix: 2683 LACNIC Region transit ASes present in the Internet Routing Table: 2288 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8771 Number of LACNIC addresses announced to Internet: 176187136 Equivalent to 10 /8s, 128 /16s and 103 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 28961 Total AfriNIC prefixes after maximum aggregation: 5728 AfriNIC Deaggregation factor: 5.06 Prefixes being announced from the AfriNIC address blocks: 36788 Unique aggregates announced from the AfriNIC address blocks: 11999 AfriNIC Region origin ASes present in the Internet Routing Table: 1711 AfriNIC Prefixes per ASN: 21.50 AfriNIC Region origin ASes announcing only one prefix: 592 AfriNIC Region transit ASes present in the Internet Routing Table: 328 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1055 Number of AfriNIC addresses announced to Internet: 108122624 Equivalent to 6 /8s, 113 /16s and 210 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks 41/8, 45/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 9446 8884 50 CHINAMOBILE-CN China Mobile Communicati 7545 5945 787 703 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4863 4192 75 ERX-CERNET-BKB China Education and Rese 7552 3632 1331 21 VIETEL-AS-AP Viettel Group, VN 7713 3506 1043 63 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3382 1874 96 VNPT-AS-VN VNPT Corp, VN 9498 2711 499 238 BBIL-AP BHARTI Airtel Ltd., IN 4766 2531 11251 593 KIXS-AS-KR Korea Telecom, KR 24560 2360 849 436 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 45090 2183 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute 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 7809 10710 2912 AMAZON-02, US 11492 4530 300 601 CABLEONE, US 7155 3895 265 33 VIASAT-SP-BACKBONE, US 22773 3693 3066 323 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3499 1320 63 SHAW, CA 16625 3468 1789 2513 AKAMAI-AS, US 749 3024 50575 2291 DNIC-AS-00749, US 7018 2586 24126 1562 ATT-INTERNET4, US 396982 2580 3494 369 GOOGLE-CLOUD-PLATFORM, US 30036 2570 368 356 MEDIACOM-ENTERPRISE-BUSINESS, 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 6966 1705 145 UNI2-AS, ES 9121 6117 1692 17 TTNET, TR 39891 4557 269 60 ALJAWWALSTC-AS, SA 20940 4055 3399 179 AKAMAI-ASN1, NL 8551 3905 374 38 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2941 2290 908 ROSTELECOM-AS, RU 47331 2792 411 2100 TTNET, TR 9009 2686 255 1361 M247, RO 34984 2253 358 609 TELLCOM-AS, TR 6849 2195 339 20 UKRTELNET, UA Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 11032 3340 585 Uninet S.A. de C.V., MX 10620 3472 507 854 Telmex Colombia S.A., CO 11830 2261 369 64 Instituto Costarricense de Electricidad 13999 2221 366 594 Mega Cable, S.A. de C.V., MX 28573 1350 2329 257 Claro NXT Telecomunicacoes Ltda, BR 6503 1297 339 517 Axtel, S.A.B. de C.V., MX 3816 1292 742 157 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6147 1151 369 22 Telefonica del Peru S.A.A., PE 11664 1136 186 465 Techtel LMDS Comunicaciones Interactiva 26615 1007 2466 43 TIM SA, BR Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24835 1544 533 30 RAYA-AS, EG 24863 1503 393 21 LINKdotNET-AS, EG 36992 1332 1517 277 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1004 67 46 ORANGE-COTE-IVOIRE, CI 36935 885 520 42 Vodafone-, EG 6713 611 1861 34 IAM-AS, MA 15399 527 54 45 WANANCHI-, KE 24757 494 73 5 EthioNet-AS, ET 37342 494 32 1 MOVITEL, MZ 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 8151 11032 3340 585 Uninet S.A. de C.V., MX 9808 9446 8884 50 CHINAMOBILE-CN China Mobile Communicati 16509 7809 10710 2912 AMAZON-02, US 12479 6966 1705 145 UNI2-AS, ES 9121 6117 1692 17 TTNET, TR 7545 5945 787 703 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4863 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4557 269 60 ALJAWWALSTC-AS, SA 11492 4530 300 601 CABLEONE, US 20940 4055 3399 179 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 9808 9446 9396 CHINAMOBILE-CN China Mobile Communications Grou 12479 6966 6821 UNI2-AS, ES 9121 6117 6100 TTNET, TR 7545 5945 5242 TPG-INTERNET-AP TPG Telecom Limited, AU 16509 7809 4897 AMAZON-02, US 4538 4863 4788 ERX-CERNET-BKB China Education and Research Net 39891 4557 4497 ALJAWWALSTC-AS, SA 11492 4530 3929 CABLEONE, US 20940 4055 3876 AKAMAI-ASN1, NL 8551 3905 3867 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 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 398083 UNALLOCATED 5.133.124.0/24 399587 UT, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 16641 UNALLOCATED 8.10.194.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.10.210.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.12.76.0/24 3356 LEVEL3, US 16641 UNALLOCATED 8.12.250.0/24 3356 LEVEL3, US 25674 UNALLOCATED 8.14.115.0/24 3356 LEVEL3, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 25674 UNALLOCATED 8.19.146.0/24 3356 LEVEL3, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.131.185.0/24 Origin: 174 COGENT-174, US 23.131.185.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.186.0/24 Origin: 174 COGENT-174, US 23.131.186.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.187.0/24 Origin: 174 COGENT-174, US 23.131.187.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.131.188.0/24 Origin: 174 COGENT-174, US 23.131.188.0/24 Transit: 2516 KDDI KDDI CORPORATION, JP 23.136.112.0/24 Origin: 54835 UNASSIGNED 23.136.112.0/24 Transit: 21559 OSNET, PR 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:13 /10:39 /11:101 /12:295 /13:582 /14:1201 /15:2039 /16:13491 /17:8321 /18:13921 /19:25219 /20:44355 /21:52331 /22:110280 /23:98380 /24:548060 /25:816 /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 6033 6966 UNI2-AS, ES 9121 5296 6117 TTNET, TR 8151 5046 11032 Uninet S.A. de C.V., MX 39891 3548 4557 ALJAWWALSTC-AS, SA 11492 3445 4530 CABLEONE, US 8551 3370 3905 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3307 3499 SHAW, CA 7155 2984 3895 VIASAT-SP-BACKBONE, US 22773 2725 3693 ASN-CXA-ALL-CCI-22773-RDC, US 47331 2413 2792 TTNET, TR Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1641 2:1236 3:168 4:5 5:4110 6:110 7:5 8:1562 9:1 11:172 12:1586 13:373 14:2372 15:286 16:79 17:371 18:421 20:243 21:4 22:188 23:6064 24:2488 25:4 27:2650 29:19 31:2500 32:99 34:9 35:106 36:1875 37:4600 38:4020 39:833 40:155 41:3957 42:1055 43:2318 44:303 45:16362 46:4196 47:382 49:1744 50:1929 51:379 52:1546 54:394 55:860 56:8 57:77 58:1745 59:1165 60:1007 61:2423 62:2623 63:1939 64:5658 65:2319 66:4909 67:3050 68:1345 69:4142 70:1254 71:661 72:2980 74:2592 75:1464 76:597 77:2386 78:3951 79:3167 80:2071 81:1828 82:1481 83:1233 84:1523 85:3716 86:746 87:1933 88:2885 89:3542 90:591 91:7631 92:1988 93:2592 94:3526 95:4863 96:1328 97:346 98:1163 99:740 100:75 101:1061 102:2511 103:30877 104:4595 105:483 106:847 107:2537 108:921 109:4356 110:2081 111:3339 112:2046 113:1556 114:1615 115:2042 116:1902 117:2562 118:2286 119:1912 120:1765 121:1114 122:2591 123:2156 124:1601 125:2351 128:1308 129:1062 130:967 131:1999 132:800 133:406 134:1907 135:298 136:886 137:927 138:2565 139:1546 140:1042 141:1485 142:1413 143:1481 144:1194 145:349 146:1854 147:1551 148:2293 149:1879 150:862 151:1135 152:1832 153:478 154:3932 155:1402 156:1655 157:1298 158:1048 159:2264 160:2557 161:1425 162:3523 163:1480 164:1612 165:1651 166:832 167:1742 168:3867 169:918 170:4582 171:886 172:3506 173:3000 174:1023 175:1159 176:3700 177:4748 178:3552 179:2152 180:2377 181:3376 182:3278 183:1932 184:2342 185:19977 186:4650 187:3925 188:4104 189:3497 190:9054 191:1428 192:10944 193:8825 194:7215 195:5117 196:3015 197:2408 198:5996 199:6094 200:7744 201:5858 202:10643 203:10040 204:4609 205:3519 206:3859 207:3421 208:4083 209:4817 210:4434 211:2503 212:4086 213:3567 214:1091 215:55 216:6610 217:2630 218:1279 219:567 220:2034 221:969 222:845 223:2060 End of report

1 0

Level 3 A and B DNS resolvers
by Josh Luthman 20 Jan '23

20 Jan '23

I'm well aware these are not to be used by the public for DNS. My only concern is that it's used as one of several external hosts to look outside of our network. This is monitored through Spectrum (Charter) in southwest Ohio. Maybe a closer server was taken offline or it was unplugged for a coffee maker. Just reaching out to see if there's any insight at all. Since ~Dec 8 it looks like we added a bit of latency: [image: image.png] DNS resolution has had quite some issues since then: [image: image.png] 4 10 ms 9 ms 8 ms lag-15.troyoh0901h.netops.charter.com [65.189.190.189] 5 17 ms 14 ms 13 ms lag-39.dytnoh5501r.netops.charter.com [65.29.38.112] 6 10 ms 10 ms 10 ms lag-28.rcr01clevohek.netops.charter.com [65.29.1.46] 7 15 ms 40 ms 10 ms lag-2-100.rpr01cleyohdh.netops.charter.com [65.29.33.239] 8 * * * Request timed out. 9 18 ms 17 ms 17 ms ae2.3601.ear1.Washington12.level3.net [4.69.148.45] 10 18 ms 17 ms 17 ms a.resolvers.level3.net [4.2.2.1] Josh Luthman 24/7 Help Desk: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

1 0

VIDEO | N86 Recap, Get Ready for N87! + More
by Nanog News 19 Jan '23

19 Jan '23

*VIDEO | Experience NANOG 86! * *Have you Registered for NANOG 87?* Our next meeting, NANOG 87 in Atlanta, is just around the corner, taking place 13 - 15 Feb. To curb your appetite until then, watch the recap of NANOG 86 in Hollywood, and experience what makes our mission and community special. You might see yourself or some familiar friendly faces! We can't wait to gather again. Cheers to connecting at NANOG 87! 👉 Standard registration rates for NANOG 87 ends 23-Jan. Don't forget to book your hotel room before the block expires on 26-Jan. *WATCH NOW* <https://www.nanog.org/news-stories/nanog-tv/nanog-86/nanog-86-recap/> *NANOG 87 Sponsorships are Still Available! * *Invest in the Strength of Community* We offer multiple opportunities for both in-person and virtual meeting sponsorships, providing your brand with the greatest level of exposure and engagement with the industry’s top minds. By aligning with professionals at the forefront of networking innovation, you’ll be recognized as an innovator, too. *MORE INFO* <https://www.nanog.org/events/sponsorship/sponsorship-opportunities/> *What's Hot on the Mailing List? * *Check out Community Trending Conversations * One of the best features of our Community Forum is that it is a graphical mirror of the mailing list. Please remember that you'll need to log in or create a NANOG account to access the Community Forum. Creating an account is quick and easy. *Check out + join the latest trending conversations, including:* - Making Use of 240/4 Netblock Replies: 338 <https://community.nanog.org/t/202203071610-ayc-re-making-use-of-240-4-netbl…> - Starlink Downlink/Internet Access Replies: 6 <https://community.nanog.org/t/starlink-downlink-internet-access/56872/4> - SDN Internet Router (Sir) Replies: 43 <https://community.nanog.org/t/sdn-internet-router-sir/56808> - Ipv4/25s and Above Replies: 101 <https://community.nanog.org/t/ipv4-25s-and-above/56632> - Large Prefix Lists/Sets on IOS-XR Replies: 18 <https://community.nanog.org/t/large-prefix-lists-sets-on-ios-xr/56719> - Large RTT Replies: 14 <https://community.nanog.org/t/large-rtt-or-why-doesnt-my-ping-traffic-get-d…> *LATEST TOPICS* <https://community.nanog.org/c/mailman/17/l/latest> *NANOG Committee: Nominations are Open! * *Nominations are Open for Six NANOG Committees* We are looking for volunteers to serve on the Program Committee, Diversity Equity and Inclusion Committee, Education Committee, Elections Committee, Mentorship Committee, and Scholarship Committee. Please consider running for a NANOG committee if you are passionate about NANOG and can commit to participating! If you know someone that you believe would be interested, please nominate them. *MORE INFO* <https://www.nanog.org/members/elections/2023-committee-nominations/> *FEATURED on NANOG TV* *Weekly NANOG TV Spotlighted Content* 🎥 This week's featured NANOG TV video (2.8K views): 👉 ▶️ Bert Hubert | NANOG 83 Keynote: Who Controls the Internet? And Should They? 'If you are not upset by the end of this presentation, you are not paying attention." This presentation discusses how Internet control is moving into the hands of browser and phone vendors. *WATCH NOW* <https://www.youtube.com/watch?v=K62fiw7inKE>

1 0

ARIN Fellowship Program for ARIN 51
by John Sweeting 17 Jan '23

17 Jan '23

NANOGers - For those folks (e.g., yourself, friends, coworkers, ...) who are looking for an in-depth mentored introduction to ARIN, please consider submitting an application to participate in the ARIN 51 Fellowship Program! Details attached below, and more online at https://www.arin.net/fellowships. Thanks! From: info(a)arin.net<mailto:info@arin.net> <mailto:info@arin.net<mailto:info@arin.net>> Sent: Thursday, January 5, 2023 12:00 PM To: arin-announce(a)arin.net<mailto:arin-announce@arin.net> <mailto:arin-announce@arin.net<mailto:arin-announce@arin.net>> Subject: [arin-announce Digest, Vol 209, Issue 2] Apply Today for the ARIN 51 Fellowship Program Learn more about Internet governance, number resource policy, and the ARIN community by becoming an ARIN Fellow. Applications for the hybrid-format ARIN 51 Fellowship Program are now open, and we encourage you to apply for this specialized, interactive learning opportunity. Apply today at https://arin.net/BeAFellow <https://arin.net/BeAFellow><https://arin.net/BeAFellow%3e> Applications are accepted from Thursday, 5 January, to Wednesday, 25 January, 2023. ARIN 51 Fellows will attend three virtual sessions before the ARIN 51 Public Policy and Members Meeting, held in Tampa, Florida from 16-19 April, and may choose to attend ARIN 51 either in person or virtually. Fellows will have the opportunity to ask questions, get feedback, and gain the knowledge and confidence to join in community discussions, propose new ideas, and become part of the future of Internet governance and policy in the ARIN region. Individuals who are 18 years of age or older and reside in the ARIN region are eligible to apply if they have a demonstrated interest in the ARIN community and its policy development processes for the management of Internet number resources. Applicants must understand the importance of ARIN?s mission and be familiar with ARIN services, including the Internet number resources it manages and the process reflected in the Number Resource Policy Manual (NRPM). To learn more about ARIN?s Fellowship Program, the selection process, and the Terms and Conditions, please visit https://www.arin.net/fellowships <https://www.arin.net/fellowships><https://www.arin.net/fellowships%3e>. Applicants that require approval from their employer prior to applying may request a customizable letter that highlights the benefits of taking part in ARIN?s Fellowship Program by emailing fellowships(a)arin.net<mailto:fellowships@arin.net> <mailto:fellowships@arin.net<mailto:fellowships@arin.net>>. If you have any other questions or need more information, please email fellowships(a)arin.net<mailto:fellowships@arin.net><mailto:fellowships@arin.net<mailto:fellowships@arin.net>>. ARIN looks forward to receiving your application soon! Regards, Amanda Gauldin Community Programs Manager American Registry for Internet Numbers (ARIN)

1 0

AS16512 Unauthorized Announcement by Lumen
by noc＠coretransit.net 17 Jan '23

17 Jan '23

Hello, My name is Austin and I work with Rackifi LLC dba CoreTransit. Our ASN is 16512. We were reassigned this ASN by ARIN. Level 3/CTL/Lumen currently has 66.223.233.0/24 https://irrexplorer.nlnog.net/prefix/66.223.233.0/24 being shown in the IRR directory for AS16512. https://irrexplorer.nlnog.net/asn/AS16512 As we operate the AS16512 ASN, we respectfully ask Lumen to remove this from their IRR records as NewEdgeNetworks does not exist, as it was sold to EarthLink and then Windstream. We do not own the /17 the subnet is part of. Thank you, Austin Ayers Rackifi LLC dba CoreTransit

2 1

ROV Deployment Survey
by Taejoong (tijay) Chung 16 Jan '23

16 Jan '23

Hi NANOG, My colleagues and I at Virginia Tech, IIJ, RIPE NCC, and MANRS have developed a new measurement platform (https://rovista.netsecurelab.org/) to measure the current deployment status of ROV. For cross-validation, we've been trying our best to collect some "ground-truth" datasets manually from rpki.exposed, personal communication, and official blog posts from network operators, but it is a bit hard to scale. It would be really appreciated if we can directly hear RPKI validation status from network operators by participating in this survey! https://www.surveymonkey.com/r/MANRSROVAdoptionSurvey The short blog post about this research is also available here: https://www.manrs.org/2023/01/take-survey-to-help-validate-rov-adoption-mea… Thank you so much for your consideration! Taejoong "Tijay" Chung, Assistant Professor Virginia Tech | Computer Science Knowledge Works II, RM 2228 2202 Kraft Drive, Blacksburg, VA 24060 (540) 231-0667| tijay(a)vt.edu

1 0

202203071610.AYC Re: Making Use of 240/4 NetBlock
by Abraham Y. Chen 16 Jan '23

16 Jan '23

Dear Colleagues: 0) I was made aware of a recent discussion on this Forum that cited our work on the 240/4 NetBlock, nicknamed EzIP (Phonetic for Easy IPv4). (Please see, at the end of this MSG, the URL to the discussion and the highlighted text where the citation was made.) 1) As the lead investigator of the EzIP Project, I would like to formally introduce our solution by bringing your attention to an overview whitepaper: https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf In a nutshell, EzIP proposes to disable the program codes in current routers that have been disabling the use of the 240/4 NetBlock. The cost of this software engineering should be minimal. The EzIP deployment architecture is the same as that of the existing CG-NAT (Carrier Grade Network Address Translation). Consequently, there is no need to modify any hardware equipment. There is an online setup description (Reference II), called RAN (Regional Area Network), that demonstrates the feasibility of this approach. 2) There are additional consequential benefits by deploying EzIP, such as those mentioned by our comment to Reference III in the above whitepaper. I look forward to addressing your thoughts. Regards, Abe (2022-03-07 17:14 EST) VP Engineering Avinta Communications, Inc. Milpitas, CA 95035 USA +1(408)942-1485 Skype: Abraham.Y.Chen eMail: AYChen(a)Avinta.com WebSite: www.Avinta.com *********************** https://mailman.nanog.org/pipermail/nanog/2021-November/216766.html Class D addresses? was: Redploying most of 127/8 as unicast public *Greg Skinner* gregskinner0 at icloud.com <mailto:nanog%40nanog.org?Subject=Re%3A%20Class%20D%20addresses%3F%20was%3A%20Redploying%20most%20of%20127/8%20as%20unicast%20public&In-Reply-To=%3CFEDBF677-BC75-47F3-A92D-2611F43283BA%40icloud.com%3E> /Mon Nov 29 18:47:14 UTC 2021/ * Previous message (by thread): Class D addresses? was: Redploying most of 127/8 as unicast public <https://mailman.nanog.org/pipermail/nanog/2021-November/216640.html> * Next message (by thread): Class E addresses? 240/4 history <https://mailman.nanog.org/pipermail/nanog/2021-November/216602.html> * *Messages sorted by:* [ date ] <https://mailman.nanog.org/pipermail/nanog/2021-November/date.html#216766> [ thread ] <https://mailman.nanog.org/pipermail/nanog/2021-November/thread.html#216766> [ subject ] <https://mailman.nanog.org/pipermail/nanog/2021-November/subject.html#216766> [ author ] <https://mailman.nanog.org/pipermail/nanog/2021-November/author.html#216766> ------------------------------------------------------------------------ >/On Nov 24, 2021, at 5:08 PM, William Herrin <bill at herrin.us <https://mailman.nanog.org/mailman/listinfo/nanog>> wrote: />//>/On Wed, Nov 24, 2021 at 4:36 PM David Conrad <drc at virtualized.org <https://mailman.nanog.org/mailman/listinfo/nanog>> wrote: />>>/I like research but what would the RIRs study? The percentage of the />>//>>/Lots of people said similar things when 1.0.0.0/8 was allocated to APNIC />>/and they said similar things when 1.1.1.0/24 was stood up as an />>/experiment by Cloudflare and APNIC, yet 1.1.1.1 seems to be pretty popular. />//>/Hi David, />//>/I don't recall there being any equipment or software compatibility />/concerns with 1.0.0.0/8. If you do, feel free to refresh my memory. As />/I recall it, there were concerns with prior local use and potential />/trash traffic. It seemed likely those concerns could be addressed with />/experiments, and the experiments in fact addressed them. />//>/The prior local use worry reared its head again with 240/4 but given />/the prior experience with 1.0.0.0/8 I don't personally believe we need />/to re-run that experiment just because the numbers are part of a />/different block. />//>//>>/Seems to me that a number of folks on this list and during this />>/discussion would disagree with a blanket assertion that 240/4 />>/is “dysfunctional on the 2021 Internet” - some of them even />>/wrote a draft discussing the possibility. />//>/Line them up. Show of hands. Who really thinks that if we assign />/240.0.0.1 to a customer tomorrow without waiting for anyone to clean />/up their software and hardware, you won't get enough complaints about />/things not working that you have to take it back and assign a />/different address instead? />//>//>>/1. Move 240/4 from "reserved" to "unallocated unicast" />>//>>/OK, but this seems like a quibble. The status for 240/4 is “ />>/RESERVED: designated by the IETF for specific non-global-unicast />>/purposes as noted.” The “as noted” part is “Future Use”. />//>/It's not a quibble. Some vendors take the current status to mean />/"treat it like unicast until we're told otherwise." Others take the />/status to mean, "packets with these addresses are bogons without a />/defined routing behavior until we're told otherwise." The result is />/incompatible behavior between vendors. Changing that direction to />/"treat it like unicast" without ambiguity is not a quibble. />//>/Regards, />/Bill Herrin />//>/-- />/William Herrin />/bill at herrin.us <https://mailman.nanog.org/mailman/listinfo/nanog> />/https://bill.herrin.us/ / For what it’s worth, I’ve been tracking this issue on other netops mailing lists. There is a recent post on the LACNOG list from Leandro Bertholdo <https://mail.lacnic.net/pipermail/lacnog/2021-November/008895.html> referencing https://datatracker.ietf.org/doc/draft-chen-ati-adaptive-ipv4-address-space/ <https://datatracker.ietf.org/doc/draft-chen-ati-adaptive-ipv4-address-space/>, a draft proposing another way to make additional IPv4 address space available I haven’t had time to read the draft closely, but I noticed that it involves the use of 240/4. Subsequent googling about the draft turned up a presentation <https://www.avinta.com/phoenix-1/home/RegionalAreaNetworkArchitecture.pdf> describing how the techniques described could be deployed. I noticed that the presentation made reference to OpenWRT, so perhaps the authors are aware of the work that the authors of the IPv4 Unicast Extensions Project have done in that area. The adaptive-ipv4 draft will expire sometime next month, so anyone interested in seeing it move forward should contact the authors. —gregbo ******************* -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

70 306

Ticketmaster contact
by Alex Buie 14 Jan '23

14 Jan '23

Hi NANOG, We're an ISP providing residential and business fixed internet services, and all of our ranges are blocked from accessing ticketmaster with the attached "Pardon the interruption, you are superhuman or a bot" message and have been for some time; customer complaint velocity has increased especially as of late so it's been a priority to try and get this working. We've done extensive checking to ensure there is no bot activity or scalping transiting our network, we aren't using cgNAT - each IP is a specific customer end installation (home/office), and we have rPKI set up. Is there anyone from Ticketmaster on list who'd be willing to contact me for a conversation to see if we can resolve this for our mutual customers? Or could anyone provide me with a decent technical contact if they might have one? I would be eternally grateful. I have tried "fan support" numerous times, which provided helpful (/s) suggestions like "try purchasing tickets over LTE", or "use a different internet connection, like at a coffee shop", or "contact your ISP" (myself? lol), depending on the day. Also tried their "Global Monitoring Support" organization by phone and by email with little success. ARIN contacts bounce back as a 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup, looks like o365 configured to not accept external messages. If you've successfully managed to work this out with them, have any tips, or recognize what WAF/engine they're using from the page layout with UUID at the bottom to help me identify who else I might try contacting to see about getting recategorized, I would really appreciate hearing from you. Thanks a bunch! Alex Buie Senior Cloud Operations Engineer 450 Century Pkwy # 100 Allen, TX 75013 D: 469-884-0225 | www.cytracom.com

2 2

starlink downlink/internet access
by Ong Beng Hui 13 Jan '23

13 Jan '23

Hi folks, Anyone know/advise if Starlink internet downlink is in US Google fiber ? I thought I saw a message before that Starlink was using Google fiber. I was referring to the actual internet transit, not the Satellite downlink station. Please advise.

6 6

NANOG Committee Nominations are Open!
by Valerie Wittkop 13 Jan '23

13 Jan '23

Dear NANOG Community, Nominations <https://www.nanog.org/members/elections/committee-nomination-process/> are now open for six NANOG Committees! We are looking for volunteers to serve on the Program Committee, Diversity Equity and Inclusion Committee, Education Committee, Elections Committee, Mentorship Committee, and Scholarship Committee. Specific committee charters and member responsibilities are linked here <https://www.nanog.org/members/elections/committee-nomination-process/> and appointments are 2-year terms, except if appointed to complete a mid-appointment term. Committee nominations will close at 9:00pm EST on Tuesday, 14 February, 2023. The NANOG Board of Directors will make appointments within the week. Emails detailing the selection results will be sent to candidates shortly thereafter, and a full announcement will be sent during the following week. Volunteer participation by members on NANOG committees is part of the essential fabric of the NANOG organization. Committee members have developed new programs, brought new ideas and new methods into practice, and helped to evolve the NANOG organization. Please consider running for a NANOG committee if you are passionate about NANOG and can commit to participating! If you know someone that you believe would be interested, please nominate them. The nomination form is linked from the 2023 Committee Nominations webpage <https://www.nanog.org/members/elections/2023-committee-nominations/> and accepts either self or 3rd party nominations. Board members are available to discuss the opportunities, so do not hesitate to reach out to them if you are interested and want to learn more. As always, you can reach us through our website contact form here <https://www.nanog.org/contact/>, or by email to either nanog-support(a)nanog.org or member-support(a)nanog.org Cheers, *Valerie Wittkop* Program Directorvwittkop(a)nanog.org | +1 734-730-0225 <+15038199432> (mobile) | www.nanog.org NANOG | 305 E. Eisenhower Pkwy, Suite 100 | Ann Arbor, MI 48108, USA ASN 19230

1 0