- Test - lists.nanog.org

Odp: Re: IRR information & BYOIP (Bring Your Own IP) with Cloud Providers
by kubanowy 22 Jan '24

22 Jan '24

Dnia 21 stycznia 2024 21:07 Christopher Morrow <morrowc.lists(a)gmail.com> napisał(a): On Fri, Jan 19, 2024, 4:55 PM Owen DeLong via NANOG < nanog(a)nanog.org > wrote: Sounds like you’ve got a weird mix of route origination. Why wouldn’t you advertise to Google via BGP and have your prefix originate from your own ASN? I think in this case the customer has their own disconnected deployment, and they are asking 396982 to announce some subset of their prefixes such that gcp gets that traffic. Yes, this is the case. GCP is advertising our prefix on our behalf. Owen On Jan 19, 2024, at 02:39, kubanowy < kubanowy(a)o2.pl > wrote: Hi, We have our own prefix assignment from ARIN. We have our infrastructure in GCP (Google Cloud Platform) where we started using BYOIP functionality (Google advertises our IPs). We followed their recommendation with ROA configuration in ARIN cloud.google.com https://cloud.google.com/vpc/docs/bring-your-own-ip#live-migration-recommen… but they don't mention if IRR (whois database) should be updated as The roa is really for two reasons: 1) tell Google you actually control that asset. 2) tell the world that 396982 is permitted to originate that prefix. Use of irr data is nice, but not required here... This is understood, however due to missing entries in IRR those tools flag those prefixes as suspicious to mismatch between what's advertised and what's in ARIN database. My goal is to avoid it. I'm looking for information on what's community approach for this. How this should be handled? well. I've checked with their support and they said no additional changes need to be done there. But currently we are in situation where ARIN's whois contains entry for our prefix with our own ASN and Google advertised to RADb entry for our prefixes with their own ASN. I don't believe to robots at google are supposed to register irr data for byoip customers... Can you mail me off list and I can go do a.little digging? ;) I haven't seen info on that in their documentation, but we did notice a new entry in RADb for prefix that we added in GCP that had MAINT set to Google. When we use online tools like irrexplorer.nlnog.net https://irrexplorer.nlnog.net/ or Cisco's CrossWork Cloud (former BGPmon), they mark our prefixes due to mismatch of ASN in those 2 databases. We haven't observed any routing issues so far (i.e. ISP not importing our prefixes), but we aim to sort this out for better credibility. I'm wondering what's community approach for updating whois databases when using BYOIP functionality with Cloud providers and if there is a risk of any potential impact if we were to change information in ARIN. Thanks

2 1

Odp: Re: IRR information & BYOIP (Bring Your Own IP) with Cloud Providers
by kubanowy 22 Jan '24

22 Jan '24

We don't advertise our prefix anymore from any actual DataCenter, we still own prefixes and ASN and GCP is only place we want to advertise it. Dnia 21 stycznia 2024 23:39 Owen DeLong <owen(a)delong.com> napisał(a): On Jan 21, 2024, at 12:07, Christopher Morrow <morrowc.lists(a)gmail.com> wrote: On Fri, Jan 19, 2024, 4:55 PM Owen DeLong via NANOG < nanog(a)nanog.org > wrote: Sounds like you’ve got a weird mix of route origination. Why wouldn’t you advertise to Google via BGP and have your prefix originate from your own ASN? I think in this case the customer has their own disconnected deployment, and they are asking 396982 to announce some subset of their prefixes such that gcp gets that traffic. If that’s the case, IMHO, the better solution is to obtain a second ASN and announce that to GCP. Create ROAs (if you want to use RPKI) accordingly. Having Google originate prefixes on your behalf that are a subset of what you are announcing is just asking for difficulties you don’t need. Owen

1 0

"Hypothetical" Datacenter Overheating
by Mike Hammett 21 Jan '24

21 Jan '24

Let's say that hypothetically, a datacenter you're in had a cooling failure and escalated to an average of 120 degrees before mitigations started having an effect. What are normal QA procedures on your behalf? What is the facility likely to be doing? What should be expected in the aftermath? ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP

19 38

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 19 Jan '24

19 Jan '24

This is an automated weekly mailing describing the state of the Global IPv4 Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG UKNOF, TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net. For historical data, please see https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 20 Jan, 2024 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: 938980 Prefixes after maximum aggregation (per Origin AS): 357247 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 455839 Total ASes present in the Internet Routing Table: 75298 Prefixes per ASN: 12.47 Origin-only ASes present in the Internet Routing Table: 64546 Origin ASes announcing only one prefix: 26557 Transit ASes present in the Internet Routing Table: 10752 Transit-only ASes present in the Internet Routing Table: 493 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 121 Max AS path prepend of ASN (150315) 116 Prefixes from unregistered ASNs in the Routing Table: 1107 Number of instances of unregistered ASNs: 1109 Number of 32-bit ASNs allocated by the RIRs: 43428 Number of 32-bit ASNs visible in the Routing Table: 35732 Prefixes from 32-bit ASNs in the Routing Table: 180291 Number of bogon 32-bit ASNs visible in the Routing Table: 31 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 482 Number of addresses announced to Internet: 3047904768 Equivalent to 181 /8s, 171 /16s and 86 /24s Percentage of available address space announced: 82.3 Percentage of allocated address space announced: 82.3 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: 309993 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 251384 Total APNIC prefixes after maximum aggregation: 72650 APNIC Deaggregation factor: 3.46 Prefixes being announced from the APNIC address blocks: 244273 Unique aggregates announced from the APNIC address blocks: 99891 APNIC Region origin ASes present in the Internet Routing Table: 13929 APNIC Prefixes per ASN: 17.54 APNIC Region origin ASes announcing only one prefix: 4198 APNIC Region transit ASes present in the Internet Routing Table: 1879 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 121 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9286 Number of APNIC addresses announced to Internet: 774863744 Equivalent to 46 /8s, 47 /16s and 123 /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: 273579 Total ARIN prefixes after maximum aggregation: 123863 ARIN Deaggregation factor: 2.21 Prefixes being announced from the ARIN address blocks: 278451 Unique aggregates announced from the ARIN address blocks: 132047 ARIN Region origin ASes present in the Internet Routing Table: 19070 ARIN Prefixes per ASN: 14.60 ARIN Region origin ASes announcing only one prefix: 6940 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: 25 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4833 Number of ARIN addresses announced to Internet: 1272419072 Equivalent to 75 /8s, 215 /16s and 147 /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: 261973 Total RIPE prefixes after maximum aggregation: 125120 RIPE Deaggregation factor: 2.09 Prefixes being announced from the RIPE address blocks: 256625 Unique aggregates announced from the RIPE address blocks: 161090 RIPE Region origin ASes present in the Internet Routing Table: 28524 RIPE Prefixes per ASN: 9.00 RIPE Region origin ASes announcing only one prefix: 12130 RIPE Region transit ASes present in the Internet Routing Table: 3959 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 37 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11546 Number of RIPE addresses announced to Internet: 714401664 Equivalent to 42 /8s, 148 /16s and 231 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-216475 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 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: 120305 Total LACNIC prefixes after maximum aggregation: 28828 LACNIC Deaggregation factor: 4.17 Prefixes being announced from the LACNIC address blocks: 118991 Unique aggregates announced from the LACNIC address blocks: 49521 LACNIC Region origin ASes present in the Internet Routing Table: 11058 LACNIC Prefixes per ASN: 10.76 LACNIC Region origin ASes announcing only one prefix: 2639 LACNIC Region transit ASes present in the Internet Routing Table: 2387 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: 8907 Number of LACNIC addresses announced to Internet: 178120704 Equivalent to 10 /8s, 157 /16s and 232 /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: 30632 Total AfriNIC prefixes after maximum aggregation: 6063 AfriNIC Deaggregation factor: 5.05 Prefixes being announced from the AfriNIC address blocks: 40158 Unique aggregates announced from the AfriNIC address blocks: 12889 AfriNIC Region origin ASes present in the Internet Routing Table: 1819 AfriNIC Prefixes per ASN: 22.08 AfriNIC Region origin ASes announcing only one prefix: 650 AfriNIC Region transit ASes present in the Internet Routing Table: 356 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: 1160 Number of AfriNIC addresses announced to Internet: 107815680 Equivalent to 6 /8s, 109 /16s and 35 /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 9801 8740 56 CHINAMOBILE-CN China Mobile Communicati 7545 5679 784 687 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4923 4192 75 ERX-CERNET-BKB China Education and Rese 18403 4571 347 25 FPT-AS-AP FPT Telecom Company, VN 7552 3865 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3592 1043 64 TELKOMNET-AS-AP PT Telekomunikasi Indon 9498 3445 499 256 BBIL-AP BHARTI Airtel Ltd., IN 45899 3276 1872 99 VNPT-AS-VN VNPT Corp, VN 24560 2682 859 361 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 4766 2295 11258 574 KIXS-AS-KR Korea Telecom, KR 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 9489 11202 3385 AMAZON-02, US 11492 4567 303 671 CABLEONE, US 7155 4177 288 96 VIASAT-SP-BACKBONE, US 6327 3569 1319 69 SHAW, CA 22773 3517 3060 305 ASN-CXA-ALL-CCI-22773-RDC, US 16625 3266 1427 2338 AKAMAI-AS, US 749 3161 54929 2413 DNIC-AS-00749, US 367 2969 3829 1433 DNIC-ASBLK-00306-00371, US 396982 2746 3639 390 GOOGLE-CLOUD-PLATFORM, US 7018 2515 23622 1579 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 7561 1714 146 UNI2-AS, ES 39891 4658 280 55 ALJAWWALSTC-AS, SA 20940 4001 3396 134 AKAMAI-ASN1, NL 9009 3329 288 1599 M247, RO 12389 2987 2302 914 ROSTELECOM-AS, RU 8551 2806 368 35 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 34984 2327 359 600 TELLCOM-AS, TR 13188 1607 100 26 TRIOLAN, UA 58224 1509 867 579 TCI, IR 8452 1484 1852 14 TE-AS TE-AS, EG 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 12320 3379 609 UNINET, MX 10620 3527 497 884 Telmex Colombia S.A., CO 13999 2494 338 637 Mega Cable, S.A. de C.V., MX 11830 2006 369 64 Instituto Costarricense de Electricidad 28573 1343 2319 238 Claro NXT Telecomunicacoes Ltda, BR 3816 1305 787 197 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 6503 1237 340 498 Axtel, S.A.B. de C.V., MX 11664 1118 178 424 Techtel LMDS Comunicaciones Interactiva 6147 1089 369 22 Telefonica del Peru S.A.A., PE 22884 1077 116 377 TOTAL PLAY TELECOMUNICACIONES SA DE CV, 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 1548 545 28 RAYA-AS, EG 24863 1527 389 16 LINKdotNET-AS, EG 36992 1363 1518 281 ETISALAT-MISR, EG 36903 1249 554 96 MT-MPLS, MA 29571 1087 70 55 ORANGE-COTE-IVOIRE, CI 36935 935 521 42 Vodafone-, EG 6713 551 1861 34 IAM-AS, MA 15399 539 56 54 WANANCHI-, KE 36914 532 82 3 KENET-AS, KE 24757 483 73 5 EthioNet-AS, ET 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 12320 3379 609 UNINET, MX 9808 9801 8740 56 CHINAMOBILE-CN China Mobile Communicati 16509 9489 11202 3385 AMAZON-02, US 12479 7561 1714 146 UNI2-AS, ES 7545 5679 784 687 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4923 4192 75 ERX-CERNET-BKB China Education and Rese 39891 4658 280 55 ALJAWWALSTC-AS, SA 18403 4571 347 25 FPT-AS-AP FPT Telecom Company, VN 11492 4567 303 671 CABLEONE, US 7155 4177 288 96 VIASAT-SP-BACKBONE, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9801 9745 CHINAMOBILE-CN China Mobile Communications Grou 12479 7561 7415 UNI2-AS, ES 16509 9489 6104 AMAZON-02, US 7545 5679 4992 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4923 4848 ERX-CERNET-BKB China Education and Research Net 39891 4658 4603 ALJAWWALSTC-AS, SA 18403 4571 4546 FPT-AS-AP FPT Telecom Company, VN 7155 4177 4081 VIASAT-SP-BACKBONE, US 11492 4567 3896 CABLEONE, US 20940 4001 3867 AKAMAI-ASN1, NL Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 65536 DOCUMENT 5.102.30.0/24 65512 -Private Use AS-, ZZ 33492 UNALLOCATED 8.6.184.0/23 33650 COMCAST-33650, US 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-DDOS-M 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 19589 UNALLOCATED 8.19.242.0/24 23314 ORLANDOTELCO, US 19589 UNALLOCATED 8.19.248.0/24 23314 ORLANDOTELCO, US 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.140.216.0/24 Origin: 27176 DATAWAGON, US 23.140.216.0/24 Transit: 20278 NEXEON, US 23.141.0.0/24 Origin: 395350 RESERVED, ZZ 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.169.168.0/24 Origin: 151188 M4NIC-AS-AP 404 Network Information Co., 23.169.168.0/24 Transit: 202400 TAIPEI101-NETWORK-LLC, GB 23.176.160.0/24 Origin: 397327 RESERVED, ZZ 23.176.160.0/24 Transit: 19108 SUDDENLINK-COMMUNICATIONS, US 23.189.192.0/24 Origin: 27593 RESERVED, ZZ 23.189.192.0/24 Transit: 174 COGENT-174, US Complete listing at https://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:14 /10:37 /11:99 /12:300 /13:579 /14:1195 /15:2068 /16:13455 /17:8244 /18:13806 /19:25069 /20:44427 /21:51917 /22:110833 /23:99044 /24:567149 /25:728 /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 6646 7561 UNI2-AS, ES 8151 6304 12320 UNINET, MX 11492 3481 4567 CABLEONE, US 6327 3374 3569 SHAW, CA 39891 3340 4658 ALJAWWALSTC-AS, SA 7155 3121 4177 VIASAT-SP-BACKBONE, US 22773 2553 3517 ASN-CXA-ALL-CCI-22773-RDC, US 8551 2282 2806 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 10620 2130 3527 Telmex Colombia S.A., CO 30036 2129 2472 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2326 2:1475 3:284 4:5 5:4430 6:163 7:6 8:1532 9:1 11:172 12:1483 13:373 14:2377 15:310 16:203 17:363 18:715 20:348 21:4 22:188 23:6614 24:2692 25:2 27:2514 29:19 31:2549 32:54 34:35 35:122 36:2142 37:4489 38:5969 39:888 40:149 41:4172 42:2219 43:2324 44:324 45:16776 46:4307 47:284 49:1912 50:1894 51:574 52:1592 54:361 55:860 56:5 57:134 58:1946 59:1208 60:1016 61:2583 62:2726 63:1910 64:5513 65:2335 66:4924 67:3044 68:1335 69:4087 70:1179 71:579 72:2912 74:2652 75:1554 76:625 77:2335 78:1829 79:2578 80:2131 81:1902 82:1522 83:1267 84:1642 85:3085 86:774 87:1960 88:1221 89:3963 90:659 91:7908 92:2177 93:2639 94:3601 95:4020 96:1289 97:318 98:1019 99:745 100:96 101:1179 102:3047 103:32545 104:4793 105:600 106:920 107:2747 108:1123 109:4048 110:2140 111:3189 112:2094 113:1796 114:1759 115:1972 116:1978 117:2634 118:2763 119:1946 120:1804 121:1324 122:2650 123:2216 124:1599 125:2839 126:28 128:1466 129:913 130:1068 131:1924 132:822 133:410 134:1708 135:308 136:921 137:1002 138:2769 139:1581 140:1308 141:1349 142:1545 143:1526 144:1004 145:343 146:1991 147:1660 148:2507 149:2435 150:1019 151:1307 152:1874 153:528 154:5622 155:1371 156:2098 157:1400 158:1087 159:2212 160:2601 161:1627 162:3605 163:1675 164:1630 165:2094 166:1079 167:1707 168:3837 169:794 170:4685 171:1012 172:3776 173:3009 174:898 175:1215 176:3627 177:4593 178:3523 179:2221 180:2363 181:3656 182:3462 183:2019 184:2279 185:20537 186:4787 187:4349 188:4007 189:3979 190:9309 191:1478 192:11030 193:8977 194:7366 195:5225 196:3180 197:2619 198:6003 199:7025 200:8074 201:6335 202:10485 203:10091 204:4595 205:3698 206:4443 207:3522 208:4111 209:4944 210:4614 211:2596 212:4225 213:3403 214:1108 215:44 216:6781 217:2773 218:1341 219:588 220:2049 221:1023 222:869 223:2226 End of report

1 0

cloudflare peering portal not loading
by P. Larivee 19 Jan '24

19 Jan '24

Hello, trying to load the Cloudflare peering portal, once logged in, it starts loading and then dies with a reactjs error. Tried on multiple browser and OS with the same result. Anyone from cloudflare that could help? > Application error: a client-side exception has occurred (see the > browser console for more information). console just shows reactjs minified errors. nothing obvious for the user. P. Larivee

1 0

okta probing
by Randy Bush 19 Jan '24

19 Jan '24

can someone explain what some child out there hopes to gain by repeatedly failing to authenticate to okta in my accound name? a couple of times a day, i have to take 40 seconds to unlock the account the kiddie has triggered. seems silly as they do not have the 2fa. it's -3c here, so i guess the clue level is going down as well as the temp. randy

3 2

Shared cache servers on an island's IXP
by Jérôme Nicolle 18 Jan '24

18 Jan '24

Hello, I'm trying to find out the best way to consolidate connectivity on an island. The current issues are : - Low redundancy of old cables (2) - Low system capacity of said cables (<=20Gbps) - Total service loss when both cables are down because of congestion on satelite backups - Sheer price of bandwidth On the plus side, there are over 5 AS on the island, an IXP and small-ish collocation capacity (approx 10kW available, could be upgraded, second site available later this year). We'd like to host cache servers and/or VMs on the IXP, with an option to anycast many services - without hijacking them, that goes without saying - such as quad-whatever DNS resolvers, NTP servers and whatever else could be useful for weather-induced disaster-recovery and/or offload cables. Do you think most CDNs, stream services and CSPs could accommodate a scenario where we'd host their gear or provide VMs for them to announce on the local route-servers ? If not, what could be a reasonable technical arrangement ? Thanks ! -- Jérôme Nicolle +33 6 19 31 27 14

6 8

Re: Shared cache servers on an island's IXP
by Jérôme Nicolle 18 Jan '24

18 Jan '24

Hi Gael, Le 18/01/2024 à 13:48, Gael Hernandez a écrit : > Friends from PCH (www.pch.net <http://www.pch.net>) operate backend > services for DNS authoritative ccTLDs and the Quad9 DNS resolver. They > would be very happy to help. I'm sure they would, I'm a big fan of their work BTW. Though hosting them in a densely connected area isn't the same as it will in remote locations, I guess there could be some work to be done to get it running properly, as Stephane wrote. How would you think we could work on that ? I mean, disconnected or extremely high latency scenarii should be on a research roadmap by SpaceX' standards, right ? ;-) Best regards, -- Jérôme Nicolle +33 6 19 31 27 14

2 1

Re: "Hypothetical" Datacenter Overheating
by Clayton Zekelman 17 Jan '24

17 Jan '24

At 09:08 AM 2024-01-15, Mike Hammett wrote: >Let's say that hypothetically, a datacenter you're in had a cooling >failure and escalated to an average of 120 degrees before >mitigations started having an effect. What are normal QA procedures >on your behalf? What is the facility likely to be doing? >What should be expected in the aftermath? One would hope they would have had disaster recovery plans to bring in outside cold air, and have executed on it quickly, rather than hoping the chillers got repaired. All our owned facilities have large outside air intakes, automatic dampers and air mixing chambers in case of mechanical cooling failure, because cooling systems are often not designed to run well in extreme cold. All of these can be manually run incase of controls failure, but people tell me I'm a little obsessive over backup plans for backup plans. You will start to see premature failure of equipment over the coming weeks/months/years. Coincidentally, we have some gear in a data centre in the Chicago area that is experiencing that sort of issue right now... :-(

10 13

Operational contact asrank.caida.org
by lsolis＠entelnet.bo 16 Jan '24

16 Jan '24

Hello Community, I am looking for an operational contact for asrank.caida.org, I urgently need them to modify an inconsistency identified in the published ranking, I have sent messages to the feedback emails indicated on the website and I didn't receive a response. Thank you very much for your help. Lia Solis

2 1