- Test - lists.nanog.org

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 26 May '23

26 May '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 27 May, 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: 924479 Prefixes after maximum aggregation (per Origin AS): 349930 Deaggregation factor: 2.64 Unique aggregates announced (without unneeded subnets): 449848 Total ASes present in the Internet Routing Table: 74440 Prefixes per ASN: 12.42 Origin-only ASes present in the Internet Routing Table: 63887 Origin ASes announcing only one prefix: 26267 Transit ASes present in the Internet Routing Table: 10553 Transit-only ASes present in the Internet Routing Table: 433 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1060 Number of instances of unregistered ASNs: 1062 Number of 32-bit ASNs allocated by the RIRs: 41953 Number of 32-bit ASNs visible in the Routing Table: 34629 Prefixes from 32-bit ASNs in the Routing Table: 172179 Number of bogon 32-bit ASNs visible in the Routing Table: 17 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 582 Number of addresses announced to Internet: 3056605440 Equivalent to 182 /8s, 48 /16s and 25 /24s Percentage of available address space announced: 82.6 Percentage of allocated address space announced: 82.6 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: 308683 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 245668 Total APNIC prefixes after maximum aggregation: 69513 APNIC Deaggregation factor: 3.53 Prefixes being announced from the APNIC address blocks: 239695 Unique aggregates announced from the APNIC address blocks: 98351 APNIC Region origin ASes present in the Internet Routing Table: 13436 APNIC Prefixes per ASN: 17.84 APNIC Region origin ASes announcing only one prefix: 3974 APNIC Region transit ASes present in the Internet Routing Table: 1808 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8740 Number of APNIC addresses announced to Internet: 773526912 Equivalent to 46 /8s, 27 /16s and 21 /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-153913 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: 269788 Total ARIN prefixes after maximum aggregation: 122784 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 272733 Unique aggregates announced from the ARIN address blocks: 130479 ARIN Region origin ASes present in the Internet Routing Table: 19113 ARIN Prefixes per ASN: 14.27 ARIN Region origin ASes announcing only one prefix: 6982 ARIN Region transit ASes present in the Internet Routing Table: 1961 Average ARIN Region AS path length visible: 3.7 Max ARIN Region AS path length visible: 24 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4805 Number of ARIN addresses announced to Internet: 1280804352 Equivalent to 76 /8s, 87 /16s and 134 /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: 259994 Total RIPE prefixes after maximum aggregation: 122472 RIPE Deaggregation factor: 2.12 Prefixes being announced from the RIPE address blocks: 255883 Unique aggregates announced from the RIPE address blocks: 158701 RIPE Region origin ASes present in the Internet Routing Table: 28316 RIPE Prefixes per ASN: 9.04 RIPE Region origin ASes announcing only one prefix: 12051 RIPE Region transit ASes present in the Internet Routing Table: 3959 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 31 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11195 Number of RIPE addresses announced to Internet: 717759104 Equivalent to 42 /8s, 200 /16s and 34 /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: 118673 Total LACNIC prefixes after maximum aggregation: 28557 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 117875 Unique aggregates announced from the LACNIC address blocks: 49457 LACNIC Region origin ASes present in the Internet Routing Table: 11010 LACNIC Prefixes per ASN: 10.71 LACNIC Region origin ASes announcing only one prefix: 2646 LACNIC Region transit ASes present in the Internet Routing Table: 2283 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 55 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8793 Number of LACNIC addresses announced to Internet: 177024256 Equivalent to 10 /8s, 141 /16s and 45 /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: 29296 Total AfriNIC prefixes after maximum aggregation: 5839 AfriNIC Deaggregation factor: 5.02 Prefixes being announced from the AfriNIC address blocks: 37711 Unique aggregates announced from the AfriNIC address blocks: 12382 AfriNIC Region origin ASes present in the Internet Routing Table: 1747 AfriNIC Prefixes per ASN: 21.59 AfriNIC Region origin ASes announcing only one prefix: 614 AfriNIC Region transit ASes present in the Internet Routing Table: 333 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 40 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1096 Number of AfriNIC addresses announced to Internet: 107095296 Equivalent to 6 /8s, 98 /16s and 37 /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 9496 8706 40 CHINAMOBILE-CN China Mobile Communicati 7545 5717 784 691 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4864 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4188 347 25 FPT-AS-AP FPT Telecom Company, VN 7713 3572 1043 66 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3380 1856 96 VNPT-AS-VN VNPT Corp, VN 7552 3232 1331 21 VIETEL-AS-AP Viettel Group, VN 9498 2964 491 239 BBIL-AP BHARTI Airtel Ltd., IN 4766 2548 11253 592 KIXS-AS-KR Korea Telecom, KR 24560 2399 836 446 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 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 8306 10783 2989 AMAZON-02, US 11492 4524 300 608 CABLEONE, US 7155 4042 282 62 VIASAT-SP-BACKBONE, US 22773 3566 3052 269 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3526 1320 64 SHAW, CA 749 3099 54980 2351 DNIC-AS-00749, US 16625 3091 1553 2339 AKAMAI-AS, US 396982 2656 3592 373 GOOGLE-CLOUD-PLATFORM, US 30036 2505 361 423 MEDIACOM-ENTERPRISE-BUSINESS, US 7018 2481 24001 1562 ATT-INTERNET4, 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 7308 1707 141 UNI2-AS, ES 39891 4897 290 61 ALJAWWALSTC-AS, SA 20940 4110 3398 161 AKAMAI-ASN1, NL 8551 3876 369 34 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2951 2292 910 ROSTELECOM-AS, RU 9009 2720 250 1409 M247, RO 34984 2279 360 608 TELLCOM-AS, TR 6849 1956 307 17 UKRTELNET, UA 58224 1829 945 534 TCI, IR 61317 1648 110 1236 ASDETUK www.heficed.com, US 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 11231 3347 607 Uninet S.A. de C.V., MX 10620 3521 508 855 Telmex Colombia S.A., CO 13999 2361 364 629 Mega Cable, S.A. de C.V., MX 11830 2270 369 64 Instituto Costarricense de Electricidad 28573 1331 2324 238 Claro NXT Telecomunicacoes Ltda, BR 3816 1297 768 173 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1294 343 510 Axtel, S.A.B. de C.V., MX 6147 1134 370 22 Telefonica del Peru S.A.A., PE 11664 1096 180 441 Techtel LMDS Comunicaciones Interactiva 26615 1038 2498 45 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 24863 1572 393 19 LINKdotNET-AS, EG 24835 1538 533 29 RAYA-AS, EG 36992 1341 1518 275 ETISALAT-MISR, EG 36903 1242 550 99 MT-MPLS, MA 29571 1030 67 47 ORANGE-COTE-IVOIRE, CI 36935 917 520 42 Vodafone-, EG 6713 550 1861 34 IAM-AS, MA 15399 526 54 49 WANANCHI-, KE 24757 488 73 5 EthioNet-AS, ET 37342 484 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 11231 3347 607 Uninet S.A. de C.V., MX 9808 9496 8706 40 CHINAMOBILE-CN China Mobile Communicati 16509 8306 10783 2989 AMAZON-02, US 12479 7308 1707 141 UNI2-AS, ES 7545 5717 784 691 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4897 290 61 ALJAWWALSTC-AS, SA 4538 4864 4192 75 ERX-CERNET-BKB China Education and Rese 11492 4524 300 608 CABLEONE, US 18403 4188 347 25 FPT-AS-AP FPT Telecom Company, VN 20940 4110 3398 161 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 9496 9456 CHINAMOBILE-CN China Mobile Communications Grou 12479 7308 7167 UNI2-AS, ES 16509 8306 5317 AMAZON-02, US 7545 5717 5026 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 4897 4836 ALJAWWALSTC-AS, SA 4538 4864 4789 ERX-CERNET-BKB China Education and Research Net 18403 4188 4163 FPT-AS-AP FPT Telecom Company, VN 7155 4042 3980 VIASAT-SP-BACKBONE, US 20940 4110 3949 AKAMAI-ASN1, NL 11492 4524 3916 CABLEONE, US Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 3507 UNALLOCATED 2.57.241.0/24 213035 AS-SERVERION Serverion B.V., 3507 UNALLOCATED 5.105.49.0/24 213035 AS-SERVERION Serverion B.V., 3507 UNALLOCATED 5.105.69.0/24 213035 AS-SERVERION Serverion B.V., 3507 UNALLOCATED 5.105.206.0/24 213035 AS-SERVERION Serverion B.V., 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 11168 SCC, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, 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.139.232.0/24 Origin: 211619 MAXKO, HR 23.139.232.0/24 Transit: 42864 GIGANET-HU GigaNet Internet Service Prov 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 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 27.100.7.0/24 Origin: 56096 UNASSIGNED 27.100.7.0/24 Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 41.57.124.0/22 Origin: 37442 UNASSIGNED 41.57.124.0/22 Transit: 37204 TELONE, ZW Complete listing at https://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:14 /10:39 /11:103 /12:301 /13:582 /14:1200 /15:2058 /16:13477 /17:8227 /18:13858 /19:25131 /20:44109 /21:51369 /22:109931 /23:98288 /24:555029 /25:747 /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 6386 7308 UNI2-AS, ES 8151 5249 11231 Uninet S.A. de C.V., MX 39891 3632 4897 ALJAWWALSTC-AS, SA 11492 3433 4524 CABLEONE, US 8551 3349 3876 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 6327 3335 3526 SHAW, CA 7155 3065 4042 VIASAT-SP-BACKBONE, US 22773 2634 3566 ASN-CXA-ALL-CCI-22773-RDC, US 30036 2161 2505 MEDIACOM-ENTERPRISE-BUSINESS, US 10620 2074 3521 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:2175 2:1312 3:181 4:5 5:4536 6:130 7:6 8:1546 9:1 11:172 12:1538 13:385 14:2306 15:304 16:191 17:374 18:421 20:258 21:4 22:188 23:6304 24:2604 25:6 27:2468 29:19 31:2486 32:80 34:21 35:112 36:1964 37:4659 38:4647 39:844 40:151 41:3924 42:1982 43:2366 44:311 45:16521 46:4353 47:363 49:1764 50:1868 51:584 52:1589 54:392 55:843 56:8 57:115 58:1891 59:1119 60:987 61:2501 62:2714 63:1940 64:5664 65:2328 66:5042 67:2927 68:1346 69:4142 70:1205 71:670 72:3003 74:2613 75:1554 76:610 77:2434 78:1822 79:3176 80:2125 81:1763 82:1488 83:1264 84:1534 85:2986 86:765 87:2010 88:1174 89:3712 90:615 91:7744 92:2065 93:2614 94:3616 95:4040 96:1298 97:336 98:1093 99:745 100:69 101:1079 102:2722 103:31356 104:4670 105:504 106:949 107:2588 108:1047 109:4415 110:2098 111:3158 112:2038 113:1801 114:1648 115:1981 116:1912 117:2508 118:2619 119:2012 120:1825 121:1131 122:2598 123:2177 124:1610 125:2502 128:1461 129:1059 130:1021 131:1988 132:815 133:422 134:1917 135:306 136:880 137:950 138:2574 139:1558 140:1248 141:1431 142:1451 143:1544 144:1152 145:346 146:1949 147:1592 148:2390 149:2251 150:875 151:1152 152:1816 153:491 154:4468 155:1438 156:1789 157:1321 158:1082 159:2237 160:2554 161:1548 162:3531 163:1533 164:1616 165:1768 166:1100 167:1736 168:3903 169:949 170:4597 171:893 172:3565 173:2962 174:1047 175:1176 176:3710 177:4699 178:3585 179:2212 180:2520 181:3501 182:3389 183:2087 184:2341 185:20285 186:4820 187:4054 188:4129 189:3668 190:9178 191:1484 192:10925 193:8873 194:7267 195:5142 196:3109 197:2373 198:5967 199:6086 200:8028 201:5889 202:10700 203:10301 204:4575 205:3704 206:4274 207:3466 208:4102 209:4894 210:4446 211:2511 212:4193 213:3619 214:1076 215:59 216:6643 217:2717 218:1291 219:580 220:1995 221:971 222:883 223:2183 End of report

1 0

Anyone from Akamai available?
by David Hubbard 26 May '23

26 May '23

Trying to determine an outage issue between Akamai and 33398; any Akamai folks on here? Thanks, David

1 0

Looking for AT&T internal routing contact
by Al 25 May '23

25 May '23

If someone knows a good AT&T routing problem contact, please let me know offline. Apparently in some cases the AT&T system routers in the business fiber division stop routing IPv6 to customers. I suspect some mid-level DHCPv6 larger block lease expiration issue, but all I know for sure is that AT&T mid-level routers start returning "address unreachable" errors for blocks of IPv6 addresses. As expected there is no working customer service infrastructure at AT&T to deal with anything other than customer modem issues and they're not allowed to escalate. If anyone has a contact, please let me know. thanks, Al Whaley Sunnyside Computing, Inc.

1 0

AS37468 (Angola Cables) - Route Leak?
by Phil Lavin 25 May '23

25 May '23

Cross-posting from outages list: Hey Folks, Seeing massive packet loss on routes from AWS to Hetzner today. First was AWS USW2 -> Hetzner (e.g. 88.99.88.69). Traffic was transiting via AS37468 (Angola Cables) in Coresite IX. Now got loss from AWS apse1/apse2. Traffic transiting via AS37468 on Equinix IX. I e-mailed Hetzner NOC but they don’t seem entirely bothered, currently. My traceroute [v0.94] jcasc-rtc01 (10.36.21.252) -> phil.lavin.me.uk <http://lavin.me.uk/> 2023-05-25T11:50:13+0000 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. ip-10-36-17-199.ap-southeast- 0.0% 18 0.1 0.6 0.1 7.7 1.8 2. ec2-18-141-171-15.ap-southeas 0.0% 18 4.3 17.5 0.9 95.7 24.0 ec2-18-141-171-1.ap-southeast-1.compute.amazonaws.com <http://ec2-18-141-171-1.ap-southeast-1.compute.amazonaws.com/> 3. (waiting for reply) 4. (waiting for reply) 5. (waiting for reply) 6. (waiting for reply) 7. (waiting for reply) 8. 100.65.10.161 0.0% 17 0.6 1.4 0.3 9.6 2.4 100.65.11.65 9. 150.222.108.75 0.0% 17 2.1 3.0 1.0 13.1 3.3 52.93.10.74 10. 150.222.108.82 0.0% 17 2.2 2.4 1.3 10.2 2.1 11. 52.93.11.115 0.0% 17 5.8 2.4 1.2 9.7 2.5 52.93.10.185 12. 37468-sg1-ix.equinix.com <http://37468-sg1-ix.equinix.com/> 68.8% 17 268.6 279.0 262.4 312.8 19.8 13. 102.219.127.3 93.8% 17 420.0 420.0 420.0 420.0 0.0 14. (waiting for reply) 15. 195.66.227.209 62.5% 17 467.9 456.9 440.3 488.2 18.5 16. core6.par.hetzner.com <http://core6.par.hetzner.com/> 75.0% 17 455.6 464.1 455.6 486.3 14.8 17. core11.nbg1.hetzner.com <http://core11.nbg1.hetzner.com/> 75.0% 17 459.5 467.5 445.9 497.3 21.8 18. core23.fsn1.hetzner.com <http://core23.fsn1.hetzner.com/> 68.8% 17 478.4 441.0 390.0 478.4 32.0 19. ex9k1.dc1.fsn1.hetzner.com <http://ex9k1.dc1.fsn1.hetzner.com/> 87.5% 17 460.4 454.2 448.1 460.4 8.7 20. vmh02.lavin.me.uk <http://vmh02.lavin.me.uk/> 75.0% 17 433.3 424.2 382.7 441.9 27.9 21. (waiting for reply) 22. http-lb-01.lavin.me.uk <http://http-lb-01.lavin.me.uk/> 75.0% 17 436.8 438.6 385.0 493.3 44.2 I’ve been out of the BGP game for a few years now. Anybody have visibility of the extent of the leaks? Phil

3 7

NANOG 88 Keynote, First ABQNOG a Success + Standard Rates Ending Sunday
by Nanog News 25 May '23

25 May '23

*Len Bosack Takes NANOG 88 Keynote Stage* *"From Data Links to Internets: A Quick Tour"* >From concept to equipment needs to various attempts to today—Bosack provides insight into the path of getting from the initial data links before the Internet to the commercial Internet the world has come to know. *REGISTER NOW <https://www.nanog.org/events/nanog-88/agenda/>* *Standard Rates for NANOG 88 Ending Sunday, 28 May* *Register Now for NANOG 88 Virtually or In-Person —12-14, June in Seattle* *REGISTER NOW <https://www.nanog.org/events/nanog-88/registration/registrant>* *First ABQNOG a Success* *“Every NOG Has Left Me with New Info, New Business Contacts, and New Friends”* We caught up with John Osmon, a seasoned industry pro and organizer of ABQNOG to talk about the new regional NOG meeting. *"This event drove home the fact that local events can be highly beneficial. National conferences are one of many ways to open your eyes to what is happening in the industry. It's also important to look around at your neighbors!"* *READ MORE * <https://nanog.org/stories/new-nog-chapter-abqnog-facilitates-successful-fir…> *Join our Whiskey Connoisseurs Affinity Group!* *Find Community in our Online Discussion Threads* The NANOG Affinity Groups are part of the Community Forum and allow our members to connect over shared interests. We need your voice! Connect with others in the tech industry and find mentorship and support while sharing your experiences. *JOIN NOW * <https://community.nanog.org/c/whiskey/42>

1 0

Flowspec Implementation on Cisco ASR
by Pascal Masha 25 May '23

25 May '23

Hi Folks, Has anyone implemented flowspec on Cisco ASR terminating PPPoE users. Flowspec rules should apply to the addresses assigned to PPPoE customers. If yes, kindly share configuration samples.. Regards Paschal Masha

1 0

Seeking recommendations - Network Eng augmentation
by Harry Hoffman 24 May '23

24 May '23

Hi Folks, If you have recommendations on companies that either provide staff augmentation or deliver management services for campus networks would you mind sharing? Cheers, Harry

1 0

Amateur radio @ nanog 88
by Lyndon Nerenberg (VE7TFX/VE6BBM) 23 May '23

23 May '23

For the hams attending 88, should we pick a simplex frequency or two to rendevouz on for beer consumption planning purposes? I'll be armed with a tribander for 146/222/440. --lyndon

1 0

Office 365 Calendar support for macOS Calendar App
by Mark Tinka 23 May '23

23 May '23

Hi all. It may just be me, or it may not, but figured I'd ask... it seems like Microsoft's 365 cloud service does not support the native Calendar app on macOS. Oddly, it works without issue for the native Calendar app in iOS. A bit of Googl'ing and speaking with some 365 customer admins. suggests that "Microsoft do not support Apple products in 365", which sounds most odd to me, as I know a number of Microsoft apps do run on macOS and iOS. Am I off the mark, are others seeing the same, is this a known issue, is it a non-issue? Mark.

3 2

Fw: [Sidrops] Estimating timeline for ASPA Deployment
by Job Snijders 19 May '23

19 May '23

Heya NANOG, I thought this email conversation might be of interest to the group: https://mailarchive.ietf.org/arch/msg/sidrops/RdbccLbXEHUrmmdIS5K9GOdJFXA/ Kind regards, Job ----- Forwarded message from Job Snijders <job(a)fastly.com> ----- Date: Fri, 19 May 2023 20:54:26 +0200 From: Job Snijders <job(a)fastly.com> To: sidrops(a)ietf.org Subject: Re: [Sidrops] Estimating timeline for ASPA Deployment Dear Tony, On Fri, May 19, 2023 at 10:18:58AM -0400, Tony Tauber wrote: > I wonder what people think of likely soonest target dates for adoption > of ASPA? ... Where do psychics go to dance? The crystal ball ;-) ... Disclaimer: The following is based on unsubstantiated information and/or my gutfeeling, I can't vouch for accuracy. I'd like to share some information categorized as 'here work needs to be done', a timeline, and a conclusion referencing earlier RPKI experiences. What needs to happen where? --------------------------- There are a few categories of 'moving parts' in the global Internet routing system that need upgrades in order for ASPA to see widespread adoption. Category | (Non-exhaustive) list of implementations --------------------------+------------------------------------------ Relaying Party packages: OpenBSD rpki-client, NLnet Labs Routinator, LACNIC/NicMX FORT, Cloudflare octorpki, Mikhail Puzanov's rpki-prover, ZDNS RPSTIR2. Signer implementations: NLnet Labs Krill, Dragon Labs rpki.net, and a number of Regional Internet Registries (RIRs) have their own in-house Signer solution. BGP implementations: OpenBSD OpenBGPD, NIC.CZ BIRD, FRRouting, Nokia SR-OS, Cisco IOS XR, Juniper Junos, and many others, see the 'BGP speakers' list at: http://largebgpcommunities.net/implementations/ Standalone RTR servers: StayRTR, NLnet Labs RTRTR, GoRTR, rpkirtr Integrated RTR servers: FORT, Routinator In order for there to be any ASPA deployment, at least one ASPA-capable implementation in all of the RP, Signer, and BGP categories is needed. Without a Signer there isn't anything for the RP to validate, without an RP there isn't any for the BGP speaker to verify BGP UPDATEs against. This is a great example of why the IETF process is so valuable: this process has brought together many stakeholders from different corners of the ecosystem each with different roles to jointly develop a solution for BGP route leaks. Timeline ======== 2023 - "the early wave": ASPA support arrives in select BGP, RP, RTR, and Signer implementations. At the moment of writing OpenBSD rpki-client & OpenBGPD; NLnet Labs Routinator, Krill & RTRTR, StayRTR, rpki-prover, and RIPE NCC have either already released ASPA-capable software or are in an advanced stage to do so. These 'early wave' implementations are incredible achievements as there weren't any examples for the developers to look at, they were building across unchartered territory. One Internet Exchange Point managed to deploy fully ASPA-capable Route Server stack using bleeding edge software, however this effort should be considered an outliner from a timeline perspective: https://mailman.nanog.org/pipermail/nanog/2023-February/221471.html 2024 - The IETF ratifies ASPA by publishing a series of RFC documents detailing the specification. While SIDROPS (this working group) at this moment in time is in the late stages of specifying the ASPA standard, the Internet Engineering Steering Group (IESG) and RFC Editor still need to review the draft documents; all in all this might take another 6-10 months (from now). BGP monitoring software such as BGPAlerter and BGP.Tools might take an interest and start using ASPA data to enhance their alerting capabilities: a growing amount of ASPA data (which can be used to identify route leaks) is becoming available through the 'delegated' (permissionless) RPKI distribution channels. 2025 - Having access to both published RFCs and multiple battle-tested RP implementations (which originated in the 'early wave'), more and more RIRs will feel comfortable scheduling and committing development time to productize an ASPA-offering for their respective RPKI dashboard/web portal/api services. Why 2025? RIRs oftentimes are somewhat conservative and like to see which way the wind blows before offering new services to their constitutes. This is very understandable as for an RIR to offer ASPA the work involved is significantly more than just developing the technical Signer software. RIRs need to design (web-based) user interfaces, which is a big hurdle because for the first time ever RIRs will move away from an 'ROA-centric' user interface to 'the RPKI offers multiple applications' (such as ASPA). As often is the case, going from 0 to 1 is extremely hard, from 1 to 2 still hard, and from 3 onwards it's smoother sailing. RIRs also need time to develop training courses for their internal staff, for external outreach such as capacity building. An RIR can't offer a new feature without explaining to their constitutes what new technology does, how to use it and how to troubleshoot it. It'll take time before RIRs feel comfortable answering questions about ASPA anyone might have. 2026 - General availability in commercial-off-the-shelf BGP speaker implementations (I expect most open-source implementations to be part of the 'early wave' or soon thereafter). Similar to how the RIRs need to develop training and documentation accessible for newcomers to ASPA, the COTS vendors need to develop ASPA-capable software, update procedures in Technical Assistance Centers, update and translate documentation to many languages, train pre-sales engineers. The larger the COTS vendor the more work incorporating a technology like ASPA as part of the product offering is. 2027 - Large nationwide and international ISPs deploy ASPA verification. By now many people will have flown around the world explaining the benefits of ASPA to ISPs both large and small, urging everyone to deploy ASPA verification and drop ASPA-invalid routes. Standing on the shoulders of giants: the published RFCs (by now 3 years old), the early wave RP/RTR implementations, the RIRs supporting ASPA in their hosted offerings since 2025, and now the recently gained access to commercially supported COTS BGP software in hand all contributed towards this moment. The large ISPs can deploy ASPA in their quality assurance environments, assess the revenue impact of deploying "if ASPA-Invalid then drop" EBGP routing policies, and schedule ASPA deployment through the 'once-a-year-sw-upgrade'-window applicable to most of their critical equipment. In conclusion: Of course - come 2027 - many people on social media might be inquiring their ISPs "why haven't you deployed ASPA-verification yet?!?!11" - without realizing that deploying something like ASPA at global scale depends on a complicated long supply chain (complicated both in the technical realm expressed as software, and in the realm of human-to-human conversation such as training and outreach). There are lessons I've learned from the global deployment of RPKI-ROV, a few of which I'd like to share publicly: There was an unfortunate long gap between people being able to create ROAs (without consequence, as for years virtually no organisation was performing RPKI-ROV), and large ISPs truly being able to deploy well-tested stable software to do Route Origin Validation at their EBGP edge; that by the time 2019/2020 rolled around this 'gap' had resulted in many BGP routes being considered ROV-invalid due to (by then inconsequential and forgotten) ROA misconfigurations. This latter aspect in turn made large ISPs extremely hesitant to deploy RPKI-ROV "invalid = drop" EBGP routing policies as a potential for customer outages (aka revenue impact) was perceived. It took building additional software (extensions to traffic analyzers such as pmacct.net and Kentik.com) to be able gauge exactly what the operational and revenue impact of deploying RPKI-ROV would be, before large ISP senior management buy-in happened. Additionally, in the global RPKI-ROV deployment the Internet routing community went from 'zero to one' in context of using *anything* RPKI-based. Much auxiliary infrastructure had to be build indirectly related to the production and consumption of ROAs: for example RIRs had to learn how to operate key materials stored in HSMs, issuance of Root CA certificates, other aspects of PKI. All in all I'm optimistic: with the collective 'first RPKI' experience under our belts, a positive outlook on ASPA-capable open source BGP software suitable for Internet Exchange Point deployments, and a solid diverse set of participants in 'the early wave'; universal deployment of ASPA-verification will be quite the journey - but hopefully smoother because of our prior experiences. この調子でがんばれ！ Job ----- End forwarded message -----

1 0