- NANOG - lists.nanog.org

Weekly Routing Table Report
by cscora＠apnic.net 26 Jun '20

26 Jun '20

This is an automated weekly mailing describing the state of the Internet 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 http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 27 Jun, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 814894 Prefixes after maximum aggregation (per Origin AS): 309638 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 397512 Total ASes present in the Internet Routing Table: 68362 Prefixes per ASN: 11.92 Origin-only ASes present in the Internet Routing Table: 58780 Origin ASes announcing only one prefix: 24483 Transit ASes present in the Internet Routing Table: 9582 Transit-only ASes present in the Internet Routing Table: 299 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 50 Max AS path prepend of ASN ( 22394) 38 Prefixes from unregistered ASNs in the Routing Table: 815 Number of instances of unregistered ASNs: 816 Number of 32-bit ASNs allocated by the RIRs: 32220 Number of 32-bit ASNs visible in the Routing Table: 26515 Prefixes from 32-bit ASNs in the Routing Table: 122091 Number of bogon 32-bit ASNs visible in the Routing Table: 11 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 537 Number of addresses announced to Internet: 2842787584 Equivalent to 169 /8s, 113 /16s and 127 /24s Percentage of available address space announced: 76.8 Percentage of allocated address space announced: 76.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 274787 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 214375 Total APNIC prefixes after maximum aggregation: 62558 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 207909 Unique aggregates announced from the APNIC address blocks: 86051 APNIC Region origin ASes present in the Internet Routing Table: 10626 APNIC Prefixes per ASN: 19.57 APNIC Region origin ASes announcing only one prefix: 2978 APNIC Region transit ASes present in the Internet Routing Table: 1585 Average APNIC Region AS path length visible: 4.7 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5710 Number of APNIC addresses announced to Internet: 769923200 Equivalent to 45 /8s, 228 /16s and 24 /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-141625 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: 238352 Total ARIN prefixes after maximum aggregation: 109528 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 235569 Unique aggregates announced from the ARIN address blocks: 119747 ARIN Region origin ASes present in the Internet Routing Table: 18526 ARIN Prefixes per ASN: 12.72 ARIN Region origin ASes announcing only one prefix: 6782 ARIN Region transit ASes present in the Internet Routing Table: 1899 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 42 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3295 Number of ARIN addresses announced to Internet: 1079433728 Equivalent to 64 /8s, 86 /16s and 218 /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-399260 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: 231374 Total RIPE prefixes after maximum aggregation: 107357 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 227988 Unique aggregates announced from the RIPE address blocks: 134369 RIPE Region origin ASes present in the Internet Routing Table: 27159 RIPE Prefixes per ASN: 8.39 RIPE Region origin ASes announcing only one prefix: 11746 RIPE Region transit ASes present in the Internet Routing Table: 3825 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9253 Number of RIPE addresses announced to Internet: 709067648 Equivalent to 42 /8s, 67 /16s and 131 /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: 106747 Total LACNIC prefixes after maximum aggregation: 24787 LACNIC Deaggregation factor: 4.31 Prefixes being announced from the LACNIC address blocks: 107886 Unique aggregates announced from the LACNIC address blocks: 46672 LACNIC Region origin ASes present in the Internet Routing Table: 9981 LACNIC Prefixes per ASN: 10.81 LACNIC Region origin ASes announcing only one prefix: 2488 LACNIC Region transit ASes present in the Internet Routing Table: 1856 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 50 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7565 Number of LACNIC addresses announced to Internet: 174461952 Equivalent to 10 /8s, 102 /16s and 20 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-272796 + 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: 23230 Total AfriNIC prefixes after maximum aggregation: 4752 AfriNIC Deaggregation factor: 4.89 Prefixes being announced from the AfriNIC address blocks: 35005 Unique aggregates announced from the AfriNIC address blocks: 10217 AfriNIC Region origin ASes present in the Internet Routing Table: 1404 AfriNIC Prefixes per ASN: 24.93 AfriNIC Region origin ASes announcing only one prefix: 489 AfriNIC Region transit ASes present in the Internet Routing Table: 277 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 692 Number of AfriNIC addresses announced to Internet: 109458432 Equivalent to 6 /8s, 134 /16s and 52 /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 7545 5537 720 648 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4743 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3435 1330 21 VIETEL-AS-AP Viettel Group, VN 45899 3168 1839 101 VNPT-AS-VN VNPT Corp, VN 7713 2700 827 527 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2558 9043 61 CMNET-GD Guangdong Mobile Communication 4766 2283 11101 553 KIXS-AS-KR Korea Telecom, KR 9498 2280 434 225 BBIL-AP BHARTI Airtel Ltd., IN 4755 2134 441 193 TATACOMM-AS TATA Communications formerl 9394 2028 4914 20 CTTNET China TieTong Telecommunications Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 11492 4450 299 643 CABLEONE, US 7155 4036 264 27 VIASAT-SP-BACKBONE, US 16509 3996 8142 1792 AMAZON-02, US 22773 3570 2968 153 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3351 1324 90 SHAW, CA 16625 3109 1620 2214 AKAMAI-AS, US 209 2420 5075 529 CENTURYLINK-US-LEGACY-QWEST, US 30036 2409 364 205 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2305 2981 1622 FRONTIER-FRTR, US 26484 2219 139 243 IKGUL-26484, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 5812 1652 135 UNI2-AS, ES 31334 5095 484 13 KABELDEUTSCHLAND-AS, DE 8551 3162 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3066 456 2075 AKAMAI-ASN1, EU 39891 2879 171 19 ALJAWWALSTC-AS, SA 12389 2549 2263 757 ROSTELECOM-AS, RU 9009 2217 233 1214 M247, GB 34984 2154 354 565 TELLCOM-AS, TR 13188 1609 100 35 TRIOLAN, UA 61317 1343 156 575 ASDETUK http://www.heficed.com, GB Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6754 3330 595 Uninet S.A. de C.V., MX 10620 3359 530 508 Telmex Colombia S.A., CO 11830 2666 369 63 Instituto Costarricense de Electricidad 6503 1718 326 387 Axtel, S.A.B. de C.V., MX 7303 1519 988 253 Telecom Argentina S.A., AR 13999 1422 512 337 Mega Cable, S.A. de C.V., MX 28573 1373 2243 216 CLARO S.A., BR 6147 1118 379 39 Telefonica del Peru S.A.A., PE 3816 1110 570 149 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 957 112 71 Alestra, S. de R.L. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1490 393 22 LINKdotNET-AS, EG 36992 1111 1539 76 ETISALAT-MISR, EG 24835 1087 474 24 RAYA-AS, EG 36903 917 480 93 MT-MPLS, MA 29571 625 68 11 ORANGE-COTE-IVOIRE, CI 6713 552 1863 34 IAM-AS, MA 15399 492 45 12 WANANCHI-, KE 37342 481 32 1 MOVITEL, MZ 36935 429 522 42 Vodafone-, EG 23889 344 231 15 MauritiusTelecom, MU Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6754 3330 595 Uninet S.A. de C.V., MX 12479 5812 1652 135 UNI2-AS, ES 7545 5537 720 648 TPG-INTERNET-AP TPG Telecom Limited, AU 31334 5095 484 13 KABELDEUTSCHLAND-AS, DE 4538 4743 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4450 299 643 CABLEONE, US 7155 4036 264 27 VIASAT-SP-BACKBONE, US 16509 3996 8142 1792 AMAZON-02, US 22773 3570 2968 153 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3435 1330 21 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 5812 5677 UNI2-AS, ES 31334 5095 5082 KABELDEUTSCHLAND-AS, DE 7545 5537 4889 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4743 4670 ERX-CERNET-BKB China Education and Research Net 7155 4036 4009 VIASAT-SP-BACKBONE, US 11492 4450 3807 CABLEONE, US 22773 3570 3417 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3435 3414 VIETEL-AS-AP Viettel Group, VN 6327 3351 3261 SHAW, CA 8551 3162 3117 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 213034 UNALLOCATED 2.56.11.0/24 34854 STACLAR-CARRIER, DE 22357 UNALLOCATED 8.7.108.0/24 3356 LEVEL3, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 62485 UNALLOCATED 8.23.229.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 26584 UNALLOCATED 8.42.62.0/23 209 CENTURYLINK-US-LEGACY-QWEST, 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 27.100.7.0/24 Origin: 56096 UNASSIGNED Transit: 45455 TH-2S1N-AP Two S One N Co Ltd, Internet 27.126.156.0/22 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 27.126.156.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 27.126.158.0/23 Origin: 55827 UNASSIGNED Transit: 9930 TTNET-MY TIME dotCom Berhad, MY 41.67.208.0/21 Origin: 15964 CAMNET-AS, CM Transit: 37282 MAINONE, NG Complete listing at http://thyme.rand.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:9 /9:11 /10:38 /11:100 /12:287 /13:578 /14:1168 /15:1912 /16:13349 /17:8215 /18:13965 /19:25900 /20:41203 /21:48482 /22:100984 /23:83519 /24:473899 /25:1275 /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 31334 4941 5095 KABELDEUTSCHLAND-AS, DE 12479 4835 5812 UNI2-AS, ES 11492 3515 4450 CABLEONE, US 6327 3140 3351 SHAW, CA 7155 3128 4036 VIASAT-SP-BACKBONE, US 22773 2779 3570 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2621 3162 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 8151 2433 6754 Uninet S.A. de C.V., MX 39891 2417 2879 ALJAWWALSTC-AS, SA 30036 2151 2409 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1754 2:1191 3:30 4:19 5:3387 6:52 8:1458 9:1 11:1 12:1777 13:512 14:2306 15:72 16:8 17:289 18:81 20:105 23:3732 24:2290 25:3 27:2552 31:3089 32:129 34:1 35:42 36:960 37:3270 38:1941 39:426 40:128 41:3685 42:900 43:2142 44:207 45:14448 46:3685 47:293 49:1465 50:1539 51:90 52:1103 54:226 55:655 56:6 57:51 58:1851 59:1175 60:756 61:2304 62:2144 63:1981 64:5227 65:2323 66:5023 67:2867 68:1178 69:3960 70:1404 71:680 72:2868 74:2577 75:1450 76:663 77:2899 78:1643 79:2380 80:1945 81:1658 82:1313 83:1328 84:1229 85:2625 86:542 87:1740 88:1142 89:2749 90:383 91:8024 92:1527 93:2507 94:2759 95:3865 96:1238 97:340 98:924 99:977 100:86 101:999 102:980 103:23778 104:3443 105:398 106:883 107:2022 108:712 109:3635 110:1850 111:2059 112:1620 113:1362 114:1540 115:1831 116:1794 117:2097 118:2145 119:1705 120:829 121:1034 122:2444 123:2072 124:1562 125:2013 128:1384 129:1210 130:655 131:1844 132:752 133:302 134:1329 135:305 136:618 137:861 138:2172 139:998 140:673 141:998 142:931 143:1253 144:1020 145:323 146:1497 147:1019 148:2117 149:1189 150:831 151:1081 152:1486 153:400 154:4694 155:1057 156:3103 157:1136 158:850 159:1977 160:1910 161:1063 162:3096 163:826 164:1467 165:1301 166:560 167:1632 168:3527 169:562 170:4226 171:777 172:1940 173:2573 174:986 175:1057 176:2580 177:4131 178:3037 179:1470 180:2274 181:2473 182:3093 183:1152 184:2414 185:16504 186:3742 187:2852 188:4105 189:2401 190:8727 191:1318 192:10376 193:7534 194:6232 195:4419 196:3278 197:2024 198:6110 199:5893 200:7203 201:5226 202:10535 203:10273 204:4566 205:3093 206:3185 207:3273 208:4065 209:4446 210:4005 211:2019 212:3391 213:3135 214:1188 215:62 216:6020 217:2406 218:854 219:616 220:2015 221:949 222:1001 223:1504 End of report

1 0

Ensuring RPKI ROAs match your routing intent
by Alex Band 26 Jun '20

26 Jun '20

Hi everyone, Over the last two years NLnet Labs has been working on free, open source RPKI software and research for the community, supported by the RIPE NCC Community Projects Fund, Brazilian NIR NIC.br and Asia Pacific RIR APNIC. I have an update that we’d like to share. When creating a ROA in RPKI, it can have an effect on one or more BGP announcements, making them either Valid, Invalid or NotFound. Understanding what exactly determines these three states is not immediately obvious, especially in the beginning. At times, this can make creating ROAs a bit of a shot in the dark. I’ve seen several examples in the past where an operator created a ROA in their RIR Portal, waited for it to be published and then checked in services like BGPMon or the HE BGP Toolkit to see if everything turned out as expected. This is why, during my time at the RIPE NCC, we put a lot of work into making it immediately obvious what the effect of a ROA is going to be on the BGP announcements with your address space. Several RIRs have followed in these footsteps since. I presented on this journey at NANOG 63 in 2015: https://archive.nanog.org/meetings/abstract?id=2500 Now, in my new adventure at NLnet Labs, we’ve gotten the same team together to make simple, intuitive ROA management for Delegated RPKI available for everyone, seamlessly across RIR regions. With Krill 0.7.1 ‘Sobremesa’ you can easily create and maintain ROAs in a user interface that incorporates all of the best practices and lessons learned over the last 10 years and monitor them in ways never before possible, such as through Prometheus. Blog post with details: http://link.medium.com/1SsTJSAvB7 All the best, Alex

3 3

Max-Prefix from IX Route-Servers - from where to get it?
by Douglas Fischer 26 Jun '20

26 Jun '20

We are creating some auxiliary to help on the deploy of our BGP Sessions. Most of the information we are getting from Peering DB. For Bilateral Sessions(over Private media, or over MPLA vlan), we use the max-prefix defined on PeeringDB profile of the partner. (And other information also, like AS-SET) But... Talking about MPLE? Where do we get the max prefix expected from the route-servers? I tried to find it on IXPDP (maintained by Euro IX / IX-F), and didn't find that information of max-prefix. https://ixpdb.euro-ix.net/en/ixpdb/route-servers/ Peering DB Searching a bit on PeeringDB I saw that some IXPs has a "NET" object created for each "IX". This is the case of DE-CIX. But there are other IXPs that don't have this parity between "NET" and "IX" objects. This is the case of IX.BR IXPs, and I Believe that is also the case of Equinix IXPs. And I Believe that the cause is that those entities use the same ASN to all the IXPs. - In IX.BR São Paulo we have around 200K routes being announced through Route-Serves. - In IX.BR Cascavel(my home city, 😍) we have around 1,5K K routes. Both IXPs we same 26162 ASN. I´m pretty sure same ambiguity occurs with other IX organizations. For example Equinix IX. The number os Routes in Ashburn is certanly different that Seoul. So, I brought a problem to discuss and find a solution. My first suggestion is: Talking about PeeringDB modeling - Create an attribute called NET on IX objects, that will point to the NET referent to that IXP Location. - Open an Exception(SPECIFIC TO IXPs) about ASN being a Unique Key - Suggest/Demands that Each IXP has their own NET Object. PS.: This solution will also solve issues like -> "Where do I get the AS-SET that contais all the NETs on that IXP?" -- Douglas Fernando Fischer Engº de Controle e Automação

1 1

Microsoft SNDS contact with a clue?
by Brian Rak 25 Jun '20

25 Jun '20

Is there anyone around from Microsoft that can help me with a SNDS verification issue? I'm having problems where the verification system is trying to use the wrong WHOIS server, and the responses I'm getting from support don't really indicate they understand the issue. I also have a different problem where I have a /17 and support keeps telling me I need to go and verify all the /23's within it... which is going to take quite awhile.

1 0

ARIN removed 154 as-set's from it's IRR a week+ ago
by Martin J. Levy 25 Jun '20

25 Jun '20

This is a quick note about as-set's. First some background. For those that followed the ARIN to ARIN & ARIN-NONAUTH split a few weeks ago, you'll know that ARIN moved around 56% of all their IRR route/route6 objects into the ARIN-NONAUTH source database. This was based on objects that are not owned within ARIN managed space. For more on this; review the ARIN mailing lists and the video from their meeting a few weeks ago. But what about all those as-set objects within ARIN IRR? This wasn't really reviewed heavily and so I thought, I'd dump some info everyone's-way. Yes there are objects and yes, some moved to ARIN-NONAUTH (and hence maybe aren't being used for route filtering anymore). First off - this data is based on the ARIN IRR database dump of 24/June/2020. You can find the current IRR data at ftp://ftp.arin.net/pub/rr/ - it's easy to download the dataset. Here's the raw numbers: $ gunzip < arin-nonauth.db.gz | egrep -i '^as-set:' | wc -l 154 $ gunzip < arin.db.gz | egrep -i '^as-set:' | wc -l 1413 $ Only around 154 as-set objects were placed into ARIN-NONAUTH. Around 9.8% of the total number of objects. Running a quick script against the RADB combined IRR database shows that of those 154 as-set objects that ARIN moved; there're 133 as-set objects that are only in ARIN-NONAUTH. An object with that name doesn't exist in any other IRR (like ARIN, ALTDB, RADB, etc.) Of the remaining 21 as-set objects, the object names (but maybe not the same content???) exist in various other IRR registries. As follows: AS-RAWBW | |ALTDB| | | AS-NFCR | |ALTDB|RADB| | AS-CTA |ARIN| | |RIPE| AS-27299 | | |RADB| | AS-33251-TRANSIT-CUSTOMERS | | |RADB| | AS-46844 | | |RADB| | AS-7349-TRANSIT-CUSTOMERS | | |RADB| | AS-ELI | | |RADB| | AS-MEEBO | | |RADB| | AS-MFT | | |RADB| | AS-28140 | | | |RIPE| AS-FUZENET | | | |RIPE| AS-MM | | | |RIPE| AS-NETLOGIC | | | |RIPE| AS-PCNET | | | |RIPE| AS-SVINE | | | |RIPE| AS-BLUENET | | |RADB|RIPE| AS-LIUXYON | |ALTDB| |RIPE| AS-NITAET | |ALTDB| |RIPE| AS-NITAETv6 | |ALTDB| |RIPE| AS-VIATEL | | |RADB|RIPE| I didn't try to check the content of these - but then again; comparing as-set's across IRRs is a thankless task - even in the best of days. So where does this leave us? We have various networks that own as-set's that are now potentially unavailable to upstreams or transit providers for creating customer filters. Keep in mind that ARIN-NONAUTH exists within RADBs IRR datasets - so it's possible that some upstream transits may use that data. Some may not. YMMV. Now onto the next step - answering that question. Of the 154 as-set objects, only 29 names appear in other as-set objects. (BTW: Thanks to "irrexplorer" for that information!). It does not mean that the 125 other entries are unused - they may be used; but not referenced by their transits (doubly so if the transit is a tier1). Focusing on the 29 that are referenced somewhere else; you end up with this listing showing the as-set object name that they appear in. If they appear in ARIN-NONAUTH that's kinda zero sum game. If they show as being referenced in other IRRs then there's hope - but not really, as they are ARIN-NONAUTH objects. Basically - however, you look at it; lesser filters are being created and maybe routing is affected. AS-23016:AS-BACKBONE ARIN-NONAUTH mentioned-in AS-23016 AS-23073 ARIN-NONAUTH mentioned-in AS-23073 AS-6653 RADB mentioned-in AS-COMCAST-IBONE AS-AHS LEVEL3 mentioned-in AS-BANDCON LEVEL3 mentioned-in AS-ISOMEDIA RADB mentioned-in AS-ISOFUSION AS-AS36412-CUSTOMERS ARIN-NONAUTH mentioned-in AS-AS36412-ALL AS-CBSI RIPE mentioned-in AS-TELIANETNA RIPE mentioned-in AS-TELIANETNA-V6 AS-CDSTEPHENS RIPE mentioned-in AS-4IXP AS-CRM-AR RIPE mentioned-in AS-TDATANETSA AS-FCH-Customers ARIN-NONAUTH mentioned-in AS-FCH AS-IMGIX NTTCOM mentioned-in AS2914:AS-US AS-IRONP-1 ALTDB mentioned-in AS-NLAYER-CUSTOMERS AS-LOGIN ARIN mentioned-in AS-DECIX-DFW ARIN mentioned-in AS-DECIX-DFW-V6 AS-MCBB-INTERNAL ARIN-NONAUTH mentioned-in AS-MCBB AS-MCBB-TRANSIT ARIN-NONAUTH mentioned-in AS-MCBB AS-MEDIA-HOSTS ALTDB mentioned-in AS-NETELLIGENT AS-MQCUSTOMERS ARIN-NONAUTH mentioned-in AS-MARQUISNET ARIN-NONAUTH mentioned-in AS35937:AS-MARQUISNET AS-PEACHNET RADB mentioned-in AS-DEFENSE AS-SAIX ARIN-NONAUTH mentioned-in AS-SAIX-ALLCUST BBOI mentioned-in AS-OCCAID6-CUSTOMERS RADB mentioned-in AS-MZIMA-CUSTOMERS RADB mentioned-in AS3491:AS-CUSTOMERS-EU RADB mentioned-in AS37271:AS-PEERS:AS5713 AS-SAIX-PEER ARIN-NONAUTH mentioned-in AS-SAIX-ALLCUST AS-SAIX-TRANSIT ARIN-NONAUTH mentioned-in AS-SAIX AS-SAIX-TRANSIT-ZA ARIN-NONAUTH mentioned-in AS-SAIX-ALLCUST BBOI mentioned-in AS-OCCAID6-CUSTOMERS AS-SELECTNET-TRANSIT ARIN-NONAUTH mentioned-in AS-SELECTNET AS-TELEFONICAMUNDO LEVEL3 mentioned-in AS-LEVEL3-POLICY-AS-SETS RIPE mentioned-in AS-TDATANETSA AS-TELNETCOMM RADB mentioned-in AS4470:AS-TORIX-PEERS AS13773:AS-CUSTOMERS ARIN-NONAUTH mentioned-in AS-TELNETCOMM AS19539:AS-IPO-US RIPE mentioned-in AS-IPO-EU AS21719:ASCUSTOMERS ARIN-NONAUTH mentioned-in AS21719:ASORIGIN AS21719:ASPEERS ARIN-NONAUTH mentioned-in AS21719:ASORIGIN AS6140:AS-CUSTOMERS BBOI mentioned-in AS-OCCAID6-CUSTOMERS (If I may interject with a commentary: what a mess!) I would urge anyone that sees their objects listed above to review their entries and if-possible delete/cleanup/consolidate whatever they have into just one IRR. I could continue deep-diving into this area; but it gets very messy very quickly. It's best to simply list what's going on and see if folks can help clean-up their own data. Summary: IRR cleanup is hard. Having *-NONAUTH database feels like a good thing; but just leaves more of a mess in the global tables. Happy IRR database hunting! Martin

1 0

lol reddit
by Michael Thomas 25 Jun '20

25 Jun '20

Apparently they've completely melted down. But them crapping out is almost a daily occurrence anyway. Does anybody have any insight as to why they are unable to keep the lights on? I mean from the outside what they do is not particularly complicated. At least Usenet had an inter-domain flood fill problem to contend with. Mike

1 0

Re: [c-nsp] Devil's Advocate - Segment Routing, Why?
by Mark Tinka 24 Jun '20

24 Jun '20

On 19/Jun/20 09:32, Saku Ytti wrote: > We need to decide if we are discussing a specific market situation or > fundamentals. Ideally we'd drive the market to what is fundamentally > most efficient, so that we pay the least amount of the kit that we > use. If we drive SRv6, we drive cost up, if we drive MPLS, we drive > cost down. > > Even today in many cases you can take a cheap L2 chip, and make it an > MPLS switch, due to them supporting VLAN swap! Which has no clue of > IPV6 or IPV4. We need a new toy. MPLS has been around far too long, and if you post web site content still talking about it or show up at conferences still talking about it, you fear that you can't sell more boxes and line cards on the back of "just" broadening carriage pipes. So we need to invent a new toy around which we can wrap a story about "adding value to your network" to "drive new business" and "reduce operating costs", to entice money to leave wallets, when all that's really still happening is the selling of more boxes and line cards, so that we can continue to broaden carriage pipes. There are very few things that have been designed well from scratch, and stand the test of time regardless of how much wind is thrown at them. MPLS is one of those things, IMHO. Nearly 20 years to the day since inception, and I still can't find another packet forwarding technology that remains as relevant and versatile as it is simple. Mark.

11 75

FCC Seeks Comment on Effects of June 15 T-Mobile Outage
by Sean Donelan 23 Jun '20

23 Jun '20

FCC Public Safety and Homeland Security Bureau Seeks Comment on Effects of June 15, 2020 T-Mobile Outage on Public Safety Entities, Government Entities, and Consumers https://www.fcc.gov/document/fcc-seeks-comment-effects-june-15-t-mobile-out… >From T-Mobile's statement: https://www.t-mobile.com/news/update-for-customers-on-network-issues "The trigger event is known to be a leased fiber circuit failure from a third party provider in the Southeast. This is something that happens on every mobile network, so we’ve worked with our vendors to build redundancy and resiliency to make sure that these types of circuit failures don’t affect customers. This redundancy failed us and resulted in an overload situation that was then compounded by other factors. This overload resulted in an IP traffic storm that spread from the Southeast to create significant capacity issues across the IMS (IP multimedia Subsystem) core network that supports VoLTE calls." Other notable national telecommunication failures AT&T - January 15 1990, AT&T Long Distance Network Collapse MCI Worldcom - August 1999, Multi-day frame-relay network failure Centurylink - December 27, 2018, 37-hour nationwide outage

1 0

Fiber in the power space
by Fletcher Kittredge 23 Jun '20

23 Jun '20

We are looking for an engineering firm with significant experience in FTTX in the power space. Extra points if you have worked with Co-ops. -- Fletcher Kittredge GWI 207-602-1134 www.gwi.net

1 0

Is there any data on packet duplication?
by Hal Murray 23 Jun '20

23 Jun '20

How often do packets magically get duplicated within the network so that the target receives 2 copies? That seems like something somebody at NANOG might have studied and given a talk on. Any suggestions for other places to look? Context is NTP. If a client gets an answer, should it keep the socket around for a short time so that any late responses or duplicates from the network don't turn into ICMP port unreachable back at the server. Nothing critical, just general clutter reduction. I have packet captures from a NTP server. I'm trying to sort things out. There are a surprising (to me) number of duplicates that arrive back-to-back, sometimes the timestamp is the same microsecond. They could come from buggy clients, but that seems like an unlikely sort of bug. -- These are my opinions. I hate spam.

7 17