- Test - lists.nanog.org

Comcast NOC - Bad IPv6 Routing
by Robert Webb 16 Feb '20

16 Feb '20

Could someone from Comcast NOC contact me off list. Looks like IPv6 routing from Richmond, VA to Grafton, WV has issues. IPSEC tunnel between gets less than 5Mbps over IPv6, switching endpoints to IPv4, I get the full 25Mbps down capability of the WV connection. Traceroute looks like below: Tracing route to 2001:558:6035:3c:79bb:f773:ab2:6bcd over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 2601:5ca:c301:4c90::1 2 11 ms 11 ms 10 ms 2001:558:4053:b::1 3 7 ms 7 ms 8 ms 2001:558:182:112::1 4 20 ms 9 ms 9 ms ae-45-ar02.staplesmllrd.va.richmond.comcast.net [2001:558:180:2005::1] 5 26 ms 30 ms 24 ms be-21508-cr02.56marietta.ga.ibone.comcast.net [2001:558:0:f787::1] 6 22 ms * 23 ms be-1202-cs02.56marietta.ga.ibone.comcast.net [2001:558:3:12::1] 7 * 28 ms * be-1211-cr11.56marietta.ga.ibone.comcast.net [2001:558:3:2::2] 8 * * * Request timed out. 9 * * * Request timed out. 10 36 ms * * be-1402-cr02.ashburn.va.ibone.comcast.net [2001:558:3:2d::2] 11 * * * Request timed out. 12 39 ms 43 ms 42 ms 2001:558:380:29c::2 13 42 ms 45 ms 50 ms te-5-1-0-cbr01.taylor.wv.pitt.comcast.net [2001:558:382:fe58::2] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out.

2 2

Peering/Transit eBGP sessions -pet or cattle?
by adamv0025＠netconsultings.com 16 Feb '20

16 Feb '20

Hi, Would like to take a poll on whether you folks tend to treat your transit/peering connections (BGP sessions in particular) as pets or rather as cattle. And I appreciate the answer could differ for transit vs peering connections. However, I'd like to ask this question through a lens of redundant vs non-redundant Internet edge devices. To explain, a. The "pet" case: Would you rather try improving the failure rate of your transit/peering connections by using resilient Control-Plane (REs/RSPs/RPs) or even designing these as link bundles over separate cards and optical modules? Is this on the bases that doesn't matter how hard you try on your end (i.e. distribute your traffic to multitude of transit and peering connections or use BFD or even BGP-PIC Edge to shuffle thing around fast, any disruption to the eBGP session itself will still hurt you in some way, (i.e. at least some partial outage for some proportion of the traffic for not insignificant period of time) until things converge in direction from The Internet back to you. b. The "cattle" case: Or would you instead rely on small-ish non-redundant HW at your internet edge rather than trying to enhance MTBF with big chassis full of redundant HW? Is this cause eventually the MTBF figure for a particular transit/peering eBGP session boils down to the MTBF of the single card or even single optical module hosting the link, (and creating bundles over separate cards -well you can never be quite sure how the setup looks like on the other end of that connection)? Or is it because the effects of a smaller/non-resilient border edge device failure is not that bad in your particular (maybe horizontally scaled) setup? Would appreciate any pointers, thank you. Thank you adam

4 9

Emergency alerts may be coming to Amazon Alexa within a year
by Sean Donelan 16 Feb '20

16 Feb '20

On this week's Federal Emergency Management Agency podcast, the director of the national emergency alerting system (IPAWS) mentions that FEMA has been in dicussions with Amazon about pushing emergency alerts to Alexa smart devices within the next year. https://www.fema.gov/media-library/assets/audio/185904 https://www.fema.gov/media-library-data/1581516469042-7fbd06067a50c2aa33fe6… You may remember last year, I was trying to get smart speaker vendors to add emergency alerts. But the program managers at those companies said they had no plans to add emergency alerts.

1 0

Weekly Routing Table Report
by cscora＠apnic.net 14 Feb '20

14 Feb '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 15 Feb, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 796453 Prefixes after maximum aggregation (per Origin AS): 302903 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 388935 Total ASes present in the Internet Routing Table: 67034 Prefixes per ASN: 11.88 Origin-only ASes present in the Internet Routing Table: 57605 Origin ASes announcing only one prefix: 24203 Transit ASes present in the Internet Routing Table: 9429 Transit-only ASes present in the Internet Routing Table: 284 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 34 Max AS path prepend of ASN (206156) 26 Prefixes from unregistered ASNs in the Routing Table: 1206 Number of instances of unregistered ASNs: 1211 Number of 32-bit ASNs allocated by the RIRs: 30539 Number of 32-bit ASNs visible in the Routing Table: 25146 Prefixes from 32-bit ASNs in the Routing Table: 115415 Number of bogon 32-bit ASNs visible in the Routing Table: 27 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 1140 Number of addresses announced to Internet: 2853769856 Equivalent to 170 /8s, 25 /16s and 18 /24s Percentage of available address space announced: 77.1 Percentage of allocated address space announced: 77.1 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.4 Total number of prefixes smaller than registry allocations: 267927 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 210542 Total APNIC prefixes after maximum aggregation: 61326 APNIC Deaggregation factor: 3.43 Prefixes being announced from the APNIC address blocks: 203888 Unique aggregates announced from the APNIC address blocks: 84909 APNIC Region origin ASes present in the Internet Routing Table: 10333 APNIC Prefixes per ASN: 19.73 APNIC Region origin ASes announcing only one prefix: 2850 APNIC Region transit ASes present in the Internet Routing Table: 1547 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5393 Number of APNIC addresses announced to Internet: 768105472 Equivalent to 45 /8s, 200 /16s and 92 /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: 234049 Total ARIN prefixes after maximum aggregation: 107635 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 231769 Unique aggregates announced from the ARIN address blocks: 117202 ARIN Region origin ASes present in the Internet Routing Table: 18401 ARIN Prefixes per ASN: 12.60 ARIN Region origin ASes announcing only one prefix: 6745 ARIN Region transit ASes present in the Internet Routing Table: 1907 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3170 Number of ARIN addresses announced to Internet: 1079268096 Equivalent to 64 /8s, 84 /16s and 83 /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: 225404 Total RIPE prefixes after maximum aggregation: 104630 RIPE Deaggregation factor: 2.15 Prefixes being announced from the RIPE address blocks: 222153 Unique aggregates announced from the RIPE address blocks: 130495 RIPE Region origin ASes present in the Internet Routing Table: 26832 RIPE Prefixes per ASN: 8.28 RIPE Region origin ASes announcing only one prefix: 11716 RIPE Region transit ASes present in the Internet Routing Table: 3797 Average RIPE Region AS path length visible: 4.5 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 8919 Number of RIPE addresses announced to Internet: 723808640 Equivalent to 43 /8s, 36 /16s and 113 /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-210331 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: 103684 Total LACNIC prefixes after maximum aggregation: 24061 LACNIC Deaggregation factor: 4.31 Prefixes being announced from the LACNIC address blocks: 104842 Unique aggregates announced from the LACNIC address blocks: 45461 LACNIC Region origin ASes present in the Internet Routing Table: 9435 LACNIC Prefixes per ASN: 11.11 LACNIC Region origin ASes announcing only one prefix: 2405 LACNIC Region transit ASes present in the Internet Routing Table: 1772 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7008 Number of LACNIC addresses announced to Internet: 174259712 Equivalent to 10 /8s, 98 /16s and 254 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + 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: 21567 Total AfriNIC prefixes after maximum aggregation: 4485 AfriNIC Deaggregation factor: 4.81 Prefixes being announced from the AfriNIC address blocks: 32661 Unique aggregates announced from the AfriNIC address blocks: 9859 AfriNIC Region origin ASes present in the Internet Routing Table: 1369 AfriNIC Prefixes per ASN: 23.86 AfriNIC Region origin ASes announcing only one prefix: 487 AfriNIC Region transit ASes present in the Internet Routing Table: 269 Average AfriNIC Region AS path length visible: 5.0 Max AfriNIC Region AS path length visible: 23 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 656 Number of AfriNIC addresses announced to Internet: 107584000 Equivalent to 6 /8s, 105 /16s and 154 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & 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 5300 658 615 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4623 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3319 1331 24 VIETEL-AS-AP Viettel Group, VN 45899 3130 1793 109 VNPT-AS-VN VNPT Corp, VN 7713 2701 831 494 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2619 9043 62 CMNET-GD Guangdong Mobile Communication 4766 2288 11102 561 KIXS-AS-KR Korea Telecom, KR 9498 2235 433 214 BBIL-AP BHARTI Airtel Ltd., IN 4755 2137 441 192 TATACOMM-AS TATA Communications formerl 9394 2077 4898 24 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 7155 4048 280 28 VIASAT-SP-BACKBONE, US 11492 3941 261 637 CABLEONE, US 16509 3826 7812 1690 AMAZON-02, US 22773 3527 2971 151 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3364 1324 92 SHAW, CA 16625 2978 1562 2136 AKAMAI-AS, US 209 2344 5075 529 CENTURYLINK-US-LEGACY-QWEST, US 30036 2305 359 94 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2149 3022 1520 FRONTIER-FRTR, US 20115 2142 2793 519 CHARTER-20115, 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 5899 1615 129 UNI2-AS, ES 31334 3947 484 13 KABELDEUTSCHLAND-AS, DE 39891 3776 203 20 ALJAWWALSTC-AS, SA 8551 3230 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2865 453 1969 AKAMAI-ASN1, US 12389 2475 2248 731 ROSTELECOM-AS, RU 34984 2070 348 557 TELLCOM-AS, TR 9009 2046 214 1093 M247, GB 9121 1917 1691 18 TTNET, TR 13188 1604 100 47 TRIOLAN, UA 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 6237 3295 601 Uninet S.A. de C.V., MX 10620 3358 533 464 Telmex Colombia S.A., CO 11830 2682 369 63 Instituto Costarricense de Electricidad 6503 1681 323 389 Axtel, S.A.B. de C.V., MX 7303 1550 1030 266 Telecom Argentina S.A., AR 28573 1327 2229 189 CLARO S.A., BR 13999 1217 506 293 Mega Cable, S.A. de C.V., MX 6147 1119 379 39 Telefonica del Peru S.A.A., PE 3816 1114 562 135 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 955 112 69 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 1235 393 22 LINKdotNET-AS, EG 24835 1070 566 24 RAYA-AS, EG 36992 1044 1535 74 ETISALAT-MISR, EG 36903 876 452 97 MT-MPLS, MA 6713 603 1863 34 IAM-AS, MA 29571 560 68 12 ORANGE-COTE-IVOIRE, CI 37342 482 32 1 MOVITEL, MZ 36935 383 522 40 Vodafone-, EG 23889 370 231 15 MauritiusTelecom, MU 15399 363 45 10 WANANCHI-, KE 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 6237 3295 601 Uninet S.A. de C.V., MX 12479 5899 1615 129 UNI2-AS, ES 7545 5300 658 615 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4623 4192 73 ERX-CERNET-BKB China Education and Rese 7155 4048 280 28 VIASAT-SP-BACKBONE, US 31334 3947 484 13 KABELDEUTSCHLAND-AS, DE 11492 3941 261 637 CABLEONE, US 16509 3826 7812 1690 AMAZON-02, US 39891 3776 203 20 ALJAWWALSTC-AS, SA 22773 3527 2971 151 ASN-CXA-ALL-CCI-22773-RDC, US 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 5899 5770 UNI2-AS, ES 7545 5300 4685 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4623 4550 ERX-CERNET-BKB China Education and Research Net 7155 4048 4020 VIASAT-SP-BACKBONE, US 31334 3947 3934 KABELDEUTSCHLAND-AS, DE 39891 3776 3756 ALJAWWALSTC-AS, SA 22773 3527 3376 ASN-CXA-ALL-CCI-22773-RDC, US 11492 3941 3304 CABLEONE, US 7552 3319 3295 VIETEL-AS-AP Viettel Group, VN 6327 3364 3272 SHAW, CA 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 17076 UNALLOCATED 8.12.244.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 27205 UNALLOCATED 8.38.16.0/21 6461 ZAYO-6461, US 27205 UNALLOCATED 8.38.16.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 27205 UNALLOCATED 8.38.20.0/22 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 14109 UNALLOCATED 8.38.252.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 23.136.224.0/24 Origin: 15206 UNASSIGNED Transit: 174 COGENT-174, US 23.137.192.0/24 Origin: 31798 CANAD-86-31798, CA Transit: 174 COGENT-174, US 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 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:10 /9:11 /10:38 /11:98 /12:285 /13:579 /14:1159 /15:1919 /16:13403 /17:8165 /18:13851 /19:25800 /20:40479 /21:47630 /22:98546 /23:81247 /24:461938 /25:1295 /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 4873 5899 UNI2-AS, ES 31334 3792 3947 KABELDEUTSCHLAND-AS, DE 6327 3153 3364 SHAW, CA 7155 3139 4048 VIASAT-SP-BACKBONE, US 11492 3075 3941 CABLEONE, US 39891 2946 3776 ALJAWWALSTC-AS, SA 22773 2742 3527 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2690 3230 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 2053 2305 MEDIACOM-ENTERPRISE-BUSINESS, US 8151 2051 6237 Uninet S.A. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1510 2:1147 3:30 4:19 5:3291 6:48 8:1378 9:1 12:1788 13:492 14:2239 15:74 16:9 17:286 18:79 20:58 23:3325 24:2640 25:4 27:2494 31:2911 32:102 35:40 36:931 37:3243 38:1842 39:315 40:132 41:3330 42:873 43:2118 44:190 45:13366 46:3653 47:276 49:1390 50:1575 51:87 52:1112 54:272 55:688 56:6 57:48 58:1877 59:1122 60:683 61:2214 62:2163 63:1943 64:5069 65:2313 66:4849 67:2854 68:1220 69:3821 70:1430 71:671 72:2775 74:2631 75:1440 76:673 77:2550 78:1973 79:2340 80:1847 81:1568 82:1205 83:1127 84:1239 85:2497 86:554 87:1706 88:1073 89:2699 90:313 91:7543 92:1493 93:2440 94:2608 95:3718 96:1012 97:337 98:965 99:967 100:86 101:1085 102:802 103:23128 104:3600 105:412 106:829 107:1927 108:709 109:3775 110:1775 111:1979 112:1564 113:1383 114:1373 115:1846 116:1773 117:2043 118:2123 119:1713 120:841 121:1035 122:2364 123:1898 124:1541 125:2029 128:1375 129:917 130:614 131:1821 132:781 133:300 134:1223 135:277 136:599 137:899 138:2188 139:986 140:592 141:875 142:870 143:1164 144:951 145:326 146:1477 147:1017 148:2063 149:1110 150:809 151:1280 152:1481 153:373 154:4716 155:903 156:3299 157:1078 158:736 159:1936 160:1732 161:1011 162:3020 163:777 164:1419 165:1237 166:544 167:1471 168:3598 169:497 170:4273 171:740 172:1878 173:2374 174:1032 175:1014 176:2620 177:4188 178:3001 179:1469 180:2171 181:2370 182:2844 183:1111 184:2396 185:16082 186:3815 187:2547 188:4064 189:2112 190:8251 191:1441 192:10266 193:7344 194:6016 195:4285 196:3393 197:1888 198:6124 199:5925 200:7148 201:5120 202:10417 203:10237 204:4548 205:3080 206:3257 207:3273 208:4001 209:4369 210:4003 211:1988 212:3254 213:3006 214:1167 215:53 216:5942 217:2343 218:880 219:603 220:1982 221:913 222:1004 223:1407 End of report

1 0

Re: akamai yesterday - what in the world was that
by Scott Weeks 13 Feb '20

13 Feb '20

-------------------------------------- On 2/11/20 6:41 PM, Tom Deligiannis wrote: > There is a major update that has released today, how's everything > looking for everyone? --------------------------------------- eyeball network here... It shifted our traffic patterns to earlier peaks. It started at 9am. The first peak was at 3pm and the main peak was at 7pm and the traffic fell back to normal loads at 1am. There was increased traffic all night, though, as our low traffic was still 4-5Gbps over normal lows at the 2-5am period. Normal peak is ~16Gbps, but this one was ~33Gbps almost all on one inexpensive link. The other main link showed and increase of about 8Gbps with a funny dip between noon and 9pm HST. scott

2 1

Anyone seeing peering/connectivity issues in San Jose?
by Brielle 13 Feb '20

13 Feb '20

Anyone else seeing peering / connectivity / peering issues in San Jose this evening? To one of my servers at Digital Ocean in San Jose from CenturyLink Boise, ID... 4 2 ms 2 ms 2 ms boi2-edge-04.inet.qwest.net [63.224.242.57] 5 14 ms 14 ms 18 ms sea-brdr-03.inet.qwest.net [67.14.41.154] 6 15 ms 14 ms 14 ms 4.68.75.121 7 * * * Request timed out. 8 * * * Request timed out. 9 31 ms 28 ms 41 ms 138.197.249.181 10 * * * Request timed out. Been doing this on and off for the last two hours or so. -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org

1 2

Re: akamai yesterday - what in the world was that
by Scott Weeks 12 Feb '20

12 Feb '20

-------------------------------------- On 2/11/20 6:41 PM, Tom Deligiannis wrote: > There is a major update that has released today, how's everything > looking for everyone? --------------------------------------- Did anyone else notice a big traffic dip from noon to 8pm local time? Strange look on the graphs. scott

1 0

Flow based architecture in data centers(more specifically Telco Clouds)
by Glen Kent 12 Feb '20

12 Feb '20

Hi, Are most of the Telco Cloud deployments envisioned to be modeled on a flow based or a non flow based architecture? I am presuming that for deeper insights into the traffic one would need a flow based architecture, but that can have scale issues (# of flows, flow setup rates, etc) and was hence checking. Thanks, Glen

5 7

Telia and Level3 in Toronto
by Drew Weaver 12 Feb '20

12 Feb '20

Has anyone else noticed a bit of a capacity or packet loss issue between Telia and Level3 in Toronto? In my specific case I was able to avoid it because I had a better route but it appears that they are trying to push more traffic through that link than it can handle. Thanks, -Drew

1 0

Customer sending blackhole route with another provider's AS
by Chris Adams 11 Feb '20

11 Feb '20

One of our multihomed customers is set up with some type of security system from another upstream that can announce blackhole routes for targeted IPs. They have a BGP policy to take those blackhole routes and add our blackhole community string so that we can drop the traffic (and we in turn translate to our transit providers). All good. However, it doesn't work, because the route the customer sends to us has the other upstream's AS as the source, and we have AS path filtering on our customer links. Is this a typical setup? Should we just accept the route(s) with another provider's AS in the path? That seems... unusual. Our internal blackhole system uses a private AS (so it can be stripped off before sending to anyone else). Just curious what others do... I always assumed AS path filtering to customer (and their downstream customers) AS was a standard best practice. -- Chris Adams <cma(a)cmadams.net>

3 2