- Test - lists.nanog.org

Cloudflare's rpki.json file is missing IPv4 ROAs longer than /24
by Steven Wallace 18 Sep '24

18 Sep '24

Greeting, Internet2 uses Cloudflare’s https://rpki.cloudflare.com/rpki.json as an alternate source for RPKI-ROA information. We recently discovered that this file omits IPv4 ROAs longer than /24. It would be helpful if it included all ROAs. Interestingly, Cloudflare’s web-based validator does include longer ROAs: https://rpki.cloudflare.com/?view=validator&validateRoute=1351_209.198.99.6… Cloudflare, any chance you could include all ROAs in this file? thanks, steve Steven Wallace Director - Routing Integrity Internet2 ssw(a)internet2.edu

5 4

RFC 9234 route leak prevention in the wild!
by Job Snijders 18 Sep '24

18 Sep '24

Dear all, I'd like to share an update on RFC 9234 deployment. RFC 9234 titled "BGP Open Policy" aka the "Only-To-Customer" (OTC) BGP Path Attribute is an anti-route-leak mechanism which is *NOT* based on RPKI! (yes ... routing security is more than just RPKI! :-) The basic idea of 9234 is that BGP routers (based on their role in the Gao-Rexford inter-domain routing model) attach a special BGP Path attribute, or take action based on the presence and contents of this BGP Path attribute - with the intention to constrain a route's propagation radius to just the downstream customer cone of the neighboring ASN. Most operators will intuitively understand that any route propagating through multiple IX route servers operated by different IXPs is a route leak: ``` IXP_1 IXP_2 / \ / \ / \ / \ ISP_A ISP_B ISP_C (receives) (leaker) (originates) ``` (figure 1. propagation from right to left; leak scenario) In the above example, ISP_A originates a route towards IXP_1's route servers, IXP_1 propagates the route to ISP_B (so far so good); but for one reason or another ISP_B subsequently continues propagation of the route towards IXP_2's route servers, who in turn propagate it to ISP_C. ISP_B is forwarding IP traffic between ISP_A and ISP_C for zero revenue. ISP_A and ISP_C are probably not expecting ISP_B to be in the middle. This situation can happen as a result of a misconfiguration in ISP_B's equipment, even when all participants use IRR & RPKI ROV to attempt to mitigate the worst routing incidents. What does it matter / impact ============================ Calgary-based YYCIX deployed RFC9234 support in late 2022/early 2023 using OpenBGPD; and FranceIX deployed support using BIRD in Q2 2024. Both IXPs configured their route servers to reject BGP routes that have an OTC attribute attached, and to attach an OTC attribute when propagating routes to the Route Server's peers. As it happens to be, currently (Mon Sep 2 12:26:50 UTC 2024) a small route leak is happening involving both YYCIX and FranceIX Route Servers via an ISP connected to both IXP's Route Servers; with the leak being stopped at YYCIX thanks to RFC 9234! Appendix A contains a table of leaked IPv4 routes. Let's zoom in on 1 entry: ``` $ bgpctl show rib 157.185.154.0/24 detail BGP routing table entry for 157.185.154.0/24 6939 38040 54994 Nexthop 206.126.225.20 (via 206.126.225.20) Neighbor 206.126.225.20 (216.218.252.194) Origin IGP, metric 1911, localpref 100, weight 0, ovs not-found, avs unknown, external, otc leak Last update: 11:58:08 ago Communities: 0:2906 0:16265 0:16276 0:18638 0:41690 0:48641 0:49029 Ext. Communities: ovs not-found Large Communities: 53339:11:1 53339:11:3 Aggregator: 54994 [163.171.131.254] OTC: 51706 ``` (figure 2. inspecting an leaked route using OpenBGPD's CLI) In figure 2. one can see the route is marked as 'otc leak', this was made possible because FranceIX's route server's attached the OTC attribute with the ASN value set to their Route Server's ASN (51706). ``` YYCIX FranceIX . x <adds OTC> \ . \ / \ ISP_A 6939_38040 54994 ``` (figure 3. right to left: real world example of blocked leak) In figure 3 AS 54994 originates 157.185.154.0/24 and propagates a route towards the FranceIX route servers. FranceIX accepts this route (probably because an IRR route object exists) and propagates it onward with the "Only-To-Customer" attribute set to 51706. The route is received by AS 38040, who appear to propagate the route to their upstream 6939. << An AS 38040 router is likely misconfigured! >> Then 6939 sends its customer's routes to the YYCIX route server, but the YYCIX route server recognizes that the route already passed through a 'valley' and thus considers this a leak; and blocks further propagation towards ISP_A. Impact with partial deployment ============================== RFC 9234 is an easy mechanism to configure and debug for both small & large network operators and IXP route server operators. In the above scenario YYCIX and FranceIX are likely the only 2 entities in the entire AS path which support RFC 9234; but we're already seeing leaks being blocked despite partial deployment! It's not hard to imagine that many IX-to-IX route leaks can be blocked with only the IXP operators themselves enabling RFC 9234 support. The world's most populair RS implementations (BIRD and OpenBGPD) already support RFC 9234! Tens of thousands of IX customers would enjoy the benefits of a few hundred IXPs taking action. RFC 9234 has no dependency on the RPKI, this means tha What can you do? ================ Just ask your vendors (your hardware routers and IXPs) to implement and deploy RFC 9234! :-) The more people ask, the more it'll bubble to the top of the priority list. The cost of implementing & deploying RFC 9234 is excellent bang for buck. Closing words ============= Shout out to our friends at FranceIX and MSK-IX for being amongst the first IXPs to deploy RFC 9234! Your effort helped reduce the potential impact of today's route leak! Kind regards, Job (YYCIX volunteer) Appendix A: ----------- Vantage point: YYCIX Route Server 1 (rs1.yycix.ca) Timestamp: Mon Sep 2 12:31:50 UTC 2024 Destination Prefix AS_PATH 102.164.129.0/24 6939 37613 6758 37649 i 102.164.139.0/24 6939 37613 6758 37649 37649 37649 37649 37649 i 102.164.140.0/24 6939 37613 6758 37649 i 102.164.141.0/24 6939 37613 6758 37649 i 102.164.182.0/24 6939 37613 6758 37649 i 154.65.33.0/24 6939 37613 6758 37649 i 154.65.34.0/24 6939 37613 6758 37649 i 154.65.35.0/24 6939 37613 6758 37649 i 154.65.36.0/24 6939 37613 6758 37649 i 154.65.37.0/24 6939 37613 6758 37649 i 154.65.38.0/24 6939 37613 6758 37649 i 154.65.39.0/24 6939 37613 6758 37649 i 154.72.35.0/24 6939 37613 37100 37027 37063 327721 i 157.185.151.0/24 6939 38040 54994 i 157.185.154.0/24 6939 38040 54994 i 163.171.164.0/24 6939 38040 54994 i 192.150.250.0/23 6939 4651 4618 4618 63529 4621 3836 i 196.50.8.0/24 6939 37613 6758 37649 i 196.50.9.0/24 6939 37613 6758 37649 i 196.50.11.0/24 6939 37613 6758 37649 37649 37649 37649 37649 i 196.50.13.0/24 6939 37613 6758 37649 37649 37649 37649 37649 i 196.50.14.0/24 6939 37613 6758 37649 i 2001:67c:15f4::/48 6939 41103 i 2401:c500:fd08::/48 6939 4637 38040 54994 i 2a01:53c0:ff03::/48 6939 4637 38040 54994 i 2a01:53c0:ff0f::/48 6939 4637 38040 54994 i 2a01:58c0::/32 6939 16347 42487 i 2a03:8920::/32 6939 41103 i 2a03:d602::/31 6939 16347 42487 i 2a03:d606::/31 6939 16347 42487 i 2a0d:ee00::/32 6939 16347 42487 i 2a0e:5b80::/29 6939 16347 42487 i 2a0e:e080::/32 6939 16347 42487 i 2a0f:c540::/29 6939 16347 42487 i

5 4

Layer 2 VPLS - Amsterdam - Singapore - LA (P2P) Multi Point to Point
by James Braunegg 17 Sep '24

17 Sep '24

Dear All I am looking for additional capacity as a Layer 2 VPLS service (Or similar) between AMS-01 EvoSwitch, SG1 Equinix Singapore and Core Site One Wilshire on a 10G port Latency between sites is important If you require any more information please just email me Please contact me off list Kindest Regards James Braunegg [cid:image001.png@01DB090F.F70AA130] 1300 769 972<tel:1300%20769%20972> / 0488 997 207<tel:1300%20769%20972> james.braunegg(a)micron21.com<mailto:james.braunegg@micron21.com> www.micron21.com/virtual-datacentre-tour <https://www.micron21.com/virtual-datacentre-tour> [cid:image002.png@01DB090F.F70AA130]<http://www.micron21.com/> [cid:image003.png@01DB090F.F70AA130]<https://www.facebook.com/micron21/> [cid:image004.png@01DB090F.F70AA130]<https://twitter.com/micron21> Follow us on m21status.com<https://m21status.com/> for important service and system updates. This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must not use, copy, distribute or disclose it to anyone other than the addressee. If you have received this message in error please return the message to the sender by replying to it and then delete the message from your computer.

1 0

Third Party VoIP Over Xfinity
by Matt Hoppes 14 Sep '24

14 Sep '24

I have an employee who has recently switched to Xfinity cable service. Ever since they switched their internet service their work phones will not stay registered for more than about 3 minutes. These same phones have been used on many ISPs without issues. The same config has been used behind multiple levels of NAT without issues. She was fine, until she switched to XFinity. Of course, XFinity support is absolutely worthless. Anyone from XFinity Tier 3 or such that might be able to offer assistance? I suspect it's something stupid with either NAT overload in the modem or the modem not keeping the SIP channels open. I've tried playing around with registration times without any success. And again, we've never had issues with these phones or this setup with any other ISP.

20 39

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 13 Sep '24

13 Sep '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 14 Sep, 2024 IPv4 BGP Table (Global) as seen at Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 959790 Prefixes after maximum aggregation (per Origin AS): 365814 Deaggregation factor: 2.62 Unique aggregates announced (without unneeded subnets): 466039 Number of IPv4 prefixes with a valid ROA: 401333 Number of IPv4 prefixes with an invalid ROA: 1266 Number of IPv4 prefixes with no ROA: 557191 Total ASes present in the Internet Routing Table: 76206 Prefixes per ASN: 12.59 Origin-only ASes present in the Internet Routing Table: 65246 Origin ASes announcing only one prefix: 26829 Transit ASes present in the Internet Routing Table: 10960 Transit-only ASes present in the Internet Routing Table: 534 Average AS path length visible in the Internet Routing Table: 5.3 Max AS path length visible: 84 Max AS path prepend of ASN (152107) 80 Prefixes from unregistered ASNs in the Routing Table: 995 Number of instances of unregistered ASNs: 1005 Number of 32-bit ASNs allocated by the RIRs: 45348 Number of 32-bit ASNs visible in the Routing Table: 37070 Prefixes from 32-bit ASNs in the Routing Table: 192329 Number of bogon 32-bit ASNs visible in the Routing Table: 47 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 571 Number of addresses announced to Internet: 3034664704 Equivalent to 180 /8s, 225 /16s and 79 /24s Percentage of available address space announced: 82.0 Percentage of allocated address space announced: 82.0 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: 313926 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 257564 Total APNIC prefixes after maximum aggregation: 75593 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 249208 Unique aggregates announced from the APNIC address blocks: 100738 APNIC Region origin ASes present in the Internet Routing Table: 14350 APNIC Prefixes per ASN: 17.37 APNIC Region origin ASes announcing only one prefix: 4370 APNIC Region transit ASes present in the Internet Routing Table: 1912 Average APNIC Region AS path length visible: 5.5 Max APNIC Region AS path length visible: 84 Number of APNIC region 32-bit ASNs visible in the Routing Table: 9765 Number of APNIC addresses announced to Internet: 762166912 Equivalent to 45 /8s, 109 /16s and 190 /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: 279829 Total ARIN prefixes after maximum aggregation: 126061 ARIN Deaggregation factor: 2.22 Prefixes being announced from the ARIN address blocks: 283753 Unique aggregates announced from the ARIN address blocks: 135048 ARIN Region origin ASes present in the Internet Routing Table: 19157 ARIN Prefixes per ASN: 14.81 ARIN Region origin ASes announcing only one prefix: 6964 ARIN Region transit ASes present in the Internet Routing Table: 2006 Average ARIN Region AS path length visible: 4.6 Max ARIN Region AS path length visible: 28 Number of ARIN region 32-bit ASNs visible in the Routing Table: 5001 Number of ARIN addresses announced to Internet: 1266977280 Equivalent to 75 /8s, 132 /16s and 138 /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-402332 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: 266620 Total RIPE prefixes after maximum aggregation: 128727 RIPE Deaggregation factor: 2.07 Prefixes being announced from the RIPE address blocks: 262945 Unique aggregates announced from the RIPE address blocks: 166902 RIPE Region origin ASes present in the Internet Routing Table: 28737 RIPE Prefixes per ASN: 9.15 RIPE Region origin ASes announcing only one prefix: 12126 RIPE Region transit ASes present in the Internet Routing Table: 3980 Average RIPE Region AS path length visible: 5.4 Max RIPE Region AS path length visible: 43 Number of RIPE region 32-bit ASNs visible in the Routing Table: 11999 Number of RIPE addresses announced to Internet: 723305088 Equivalent to 43 /8s, 28 /16s and 194 /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: 122573 Total LACNIC prefixes after maximum aggregation: 28363 LACNIC Deaggregation factor: 4.32 Prefixes being announced from the LACNIC address blocks: 120390 Unique aggregates announced from the LACNIC address blocks: 48507 LACNIC Region origin ASes present in the Internet Routing Table: 11157 LACNIC Prefixes per ASN: 10.79 LACNIC Region origin ASes announcing only one prefix: 2686 LACNIC Region transit ASes present in the Internet Routing Table: 2485 Average LACNIC Region AS path length visible: 5.9 Max LACNIC Region AS path length visible: 61 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 9061 Number of LACNIC addresses announced to Internet: 177722880 Equivalent to 10 /8s, 151 /16s and 214 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-274844 + 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: 32209 Total AfriNIC prefixes after maximum aggregation: 6428 AfriNIC Deaggregation factor: 5.01 Prefixes being announced from the AfriNIC address blocks: 42923 Unique aggregates announced from the AfriNIC address blocks: 14368 AfriNIC Region origin ASes present in the Internet Routing Table: 1880 AfriNIC Prefixes per ASN: 22.83 AfriNIC Region origin ASes announcing only one prefix: 683 AfriNIC Region transit ASes present in the Internet Routing Table: 367 Average AfriNIC Region AS path length visible: 6.0 Max AfriNIC Region AS path length visible: 30 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 1244 Number of AfriNIC addresses announced to Internet: 104182784 Equivalent to 6 /8s, 53 /16s and 180 /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 9947 8747 80 CHINAMOBILE-CN China Mobile Communication 7545 5706 840 658 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4949 4192 74 ERX-CERNET-BKB China Education and Resear 18403 4298 347 23 FPT-AS-AP FPT Telecom Company, VN 7552 3976 1331 21 VIETEL-AS-AP Viettel Group, VN 9498 3789 508 261 BBIL-AP BHARTI Airtel Ltd., IN 7713 3617 1044 66 TELKOMNET-AS-AP PT Telekomunikasi Indones 45899 3261 1841 105 VNPT-AS-VN VNPT Corp, VN 24560 2808 841 467 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd., 4766 2273 11520 578 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 10716 11807 3745 AMAZON-02, US 11492 4642 308 545 CABLEONE, US 7155 4169 287 89 VIASAT-SP-BACKBONE, US 174 3924 8780 906 COGENT-174, US 6327 3602 1320 79 SHAW, CA 749 3484 55080 2707 DNIC-AS-00749, US 22773 3423 3035 187 ASN-CXA-ALL-CCI-22773-RDC, US 7018 3085 23684 1932 ATT-INTERNET4, US 16625 2856 1268 2131 AKAMAI-AS, US 396982 2814 3570 432 GOOGLE-CLOUD-PLATFORM, 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 7637 1708 145 UNI2-AS, ES 39891 4466 269 55 ALJAWWALSTC-AS, SA 20940 3826 3395 129 AKAMAI-ASN1, NL 9009 3672 313 1863 M247, RO 12389 2938 2295 888 ROSTELECOM-AS, RU 34984 2334 359 585 TELLCOM-AS, TR 212238 1810 129 1333 CDNEXT, GB 13188 1607 100 26 TRIOLAN, UA 8452 1580 1852 14 TE-AS TE-AS, EG 62240 1409 93 672 CLOUVIDER Clouvider - Global ASN, GB 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 11692 3251 496 UNINET, MX 10620 3543 494 935 Telmex Colombia S.A., CO 13999 2552 534 364 Mega Cable, S.A. de C.V., MX 11830 2009 369 64 Instituto Costarricense de Electricidad y 28573 1339 2309 261 Claro NXT Telecomunicacoes Ltda, BR 3816 1317 776 204 COLOMBIA TELECOMUNICACIONES S.A. ESP, CO 11664 1180 278 33 Techtel LMDS Comunicaciones Interactivas 6503 1149 374 163 Axtel, S.A.B. de C.V., MX 6147 1103 369 22 Telefonica del Peru S.A.A., PE 22884 1068 96 374 TOTAL PLAY TELECOMUNICACIONES SA DE CV, M 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 1611 593 29 RAYA-AS, EG 24863 1598 389 18 LINKdotNET-AS, EG 36992 1411 1519 282 ETISALAT-MISR, EG 29571 1336 85 65 ORANGE-COTE-IVOIRE, CI 36903 1249 554 96 MT-MPLS, MA 36935 953 523 48 Vodafone-, EG 6713 557 1861 35 IAM-AS, MA 36914 545 82 3 KENET-AS, KE 15399 512 57 58 WANANCHI-, KE 24757 438 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 11692 3251 496 UNINET, MX 16509 10716 11807 3745 AMAZON-02, US 9808 9947 8747 80 CHINAMOBILE-CN China Mobile Communication 12479 7637 1708 145 UNI2-AS, ES 7545 5706 840 658 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4949 4192 74 ERX-CERNET-BKB China Education and Resear 11492 4642 308 545 CABLEONE, US 39891 4466 269 55 ALJAWWALSTC-AS, SA 18403 4298 347 23 FPT-AS-AP FPT Telecom Company, VN 7155 4169 287 89 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 9947 9867 CHINAMOBILE-CN China Mobile Communications Grou 12479 7637 7492 UNI2-AS, ES 16509 10716 6971 AMAZON-02, US 7545 5706 5048 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4949 4875 ERX-CERNET-BKB China Education and Research Net 39891 4466 4411 ALJAWWALSTC-AS, SA 18403 4298 4275 FPT-AS-AP FPT Telecom Company, VN 11492 4642 4097 CABLEONE, US 7155 4169 4080 VIASAT-SP-BACKBONE, US 7552 3976 3955 VIETEL-AS-AP Viettel Group, VN 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 33123 UNALLOCATED 8.10.69.0/24 174 COGENT-174, US 12169 UNALLOCATED 8.15.207.0/24 32787 PROLEXIC-TECHNOLOGIES-D 40493 UNALLOCATED 8.17.26.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.17.66.0/24 701 UUNET, US 53775 UNALLOCATED 8.20.88.0/24 7029 WINDSTREAM, US 393266 UNALLOCATED 8.23.52.0/24 46887 CROWNCASTLE-AS46887, US 396894 UNALLOCATED 8.28.201.0/24 46887 CROWNCASTLE-AS46887, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 3356 LEVEL3, US 46639 UNALLOCATED 8.38.73.0/24 3356 LEVEL3, 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 14.192.20.0/22 Origin: 26658 HENGTONG-IDC-LLC, US 14.192.20.0/22 Transit: 6939 HURRICANE, US 23.137.192.0/24 Origin: 31798 DATACITY, CA 23.137.192.0/24 Transit: 21949 BEANFIELD, CA 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.152.48.0/24 Origin: 46167 RESERVED, ZZ 23.152.48.0/24 Transit: 7018 ATT-INTERNET4, 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:16 /10:37 /11:92 /12:295 /13:575 /14:1167 /15:2070 /16:13236 /17:8267 /18:13752 /19:24653 /20:44583 /21:52038 /22:111939 /23:100376 /24:585962 /25:716 /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 6692 7637 UNI2-AS, ES 8151 5861 11692 UNINET, MX 11492 3553 4642 CABLEONE, US 6327 3397 3602 SHAW, CA 39891 3356 4466 ALJAWWALSTC-AS, SA 7155 3113 4169 VIASAT-SP-BACKBONE, US 22773 2558 3423 ASN-CXA-ALL-CCI-22773-RDC, US 10620 2172 3543 Telmex Colombia S.A., CO 30036 2163 2501 MEDIACOM-ENTERPRISE-BUSINESS, US 16509 2162 10716 AMAZON-02, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:2309 2:1523 3:470 4:7 5:4482 6:161 7:6 8:1514 9:1 11:172 12:1428 13:375 14:2409 15:328 16:259 17:361 18:884 20:408 21:4 22:188 23:6858 24:2679 25:2 27:2573 29:19 31:2727 32:47 34:66 35:139 36:2370 37:4498 38:8535 39:916 40:150 41:4116 42:1983 43:2450 44:332 45:17538 46:4609 47:298 49:1997 50:1877 51:574 52:1581 54:316 55:957 56:8 57:216 58:2249 59:1267 60:1065 61:2731 62:2777 63:1850 64:5436 65:2277 66:4666 67:3028 68:1342 69:4004 70:1144 71:566 72:2856 74:2669 75:1568 76:622 77:2536 78:1857 79:1568 80:2209 81:2022 82:1687 83:1373 84:1763 85:3167 86:995 87:2331 88:1251 89:4311 90:681 91:8229 92:2491 93:2763 94:3777 95:4278 96:1274 97:316 98:1067 99:737 100:73 101:1166 102:3376 103:32302 104:4377 105:705 106:993 107:2383 108:1168 109:3950 110:2134 111:3296 112:2059 113:1820 114:1896 115:2094 116:1987 117:2676 118:2871 119:1981 120:1833 121:1416 122:2712 123:2163 124:1636 125:2854 126:64 128:1405 129:943 130:1222 131:1858 132:826 133:428 134:1513 135:310 136:1199 137:1103 138:2849 139:1519 140:1448 141:1448 142:1742 143:1616 144:1027 145:366 146:2093 147:2039 148:2542 149:2806 150:1068 151:1368 152:2104 153:502 154:6536 155:1437 156:2451 157:1807 158:1191 159:2451 160:3069 161:1707 162:3558 163:1761 164:1693 165:2143 166:1314 167:1853 168:4064 169:805 170:4945 171:1049 172:3910 173:3096 174:904 175:1233 176:3460 177:4795 178:3599 179:2182 180:2457 181:3897 182:3321 183:2040 184:2253 185:21055 186:5023 187:4270 188:4120 189:4141 190:9616 191:1495 192:11073 193:9244 194:7544 195:5402 196:3230 197:2997 198:6051 199:8109 200:8200 201:6358 202:10526 203:10370 204:4611 205:3696 206:4528 207:3645 208:4190 209:5133 210:4777 211:2664 212:4437 213:3671 214:1060 215:63 216:6703 217:2947 218:1413 219:556 220:2034 221:1047 222:874 223:2259 End of report

1 0

Vote Now: Color of N92 T-Shirt, Sneak Peek of Agenda + Video - Why NANOG?
by Nanog News 12 Sep '24

12 Sep '24

*Video — "Why NANOG?" Hear from a Woman in Tech **We asked Women in Tech Attendee DE-CIX's Kelly Sieben * A key part of NANOG’s evolution is the growing impact of women in tech, who are now playing a crucial role in shaping the future of Internet infrastructure and network operations. We asked an attendee of our last event Why NANOG? Here's what she had to say! Each meeting features a Women in Tech Mixer, offering important opportunities for networking, mentorship, and professional development. Our next WIT Mixer will be held on Sunday, 20, Oct. from 5-6:30. Please plan to arrive early before the conference. *WATCH NOW <https://nanog.org/stories/nanog-tv/why-nanog-women-in-tech/>* *Sneak Peek of Agenda for NANOG 92! * *Have you Registered Yet for Our Next Meeting in Toronto?* Coming to the NANOG 92 Stage in Toronto 21-23 October. More talks will be listed as the Program Committee accepts submissions. - IPv6 Familiarity Training - Create ROAs Today + Secure Your Resources with ARIN's RPKI Services - Routing Security: Fostering Continuous Improvement - The DNS Root Server System Messaging Challenge - BGP Flowspec Doesn't Suck. You're Just Doing it Wrong - + More *VIEW MORE <https://nanog.org/events/nanog-92/>* *Vote Now: What Color Would You Like Your NANOG 92 T-Shirt?* *Deadline for Voting is Monday — Don't Wait! * We need some fashion advice. Vote in our poll on your favorite color for our next meeting's T-Shirt TODAY. Deadline for print is Monday, 16, Sept. by 5 pm PST — so don't wait! ***Please Note. You must be a registered attendee + logged in to vote. *VOTE NOW <https://nanog.org/events/nanog-92/t-shirt-color-survey/>*

1 0

OIX (formerly Open-IX) Document Development Mailing List (Invitation to Join)
by Chris Grundemann 12 Sep '24

12 Sep '24

Hello NANOG, This message is being sent in my capacity as the Chair of the Board of OIX. We (OIX) have some proposed updates to standards documents that affect this community. As such, we would like to invite anyone and everyone interested to subscribe to the OIX DDP mailing list. The sole purpose of this OIX DDP mailing list is to discuss changes to standards and/or BCOPs within the scope of OIX. To ensure that all documents are created and updated in an open, community-led, transparent, and bottom-up manner, we need as many eyes on the process as possible. Thanks in advance - mailing list details follow. -- The OIX Document Development Process (OIX DDP) is the process by which current Standards and best current operational practices (BCOPs) for the operation of the Internet, and connected networks, are documented by the Global Network Engineering Community (GNEC). These OIX documents are developed and published in an open, transparent, bottom-up, and ongoing manner designed to yield functional documentation that is accessible to all. To support this, OIX maintains an OIX DDP mailing list for public discussions of proposed documents and/or changes to published documents. The list address is: oix-ddp(a)mailman.swcp.com If you're familiar with mailman, the various associated addresses are all there too. Most notably: oix-ddp-subscribe(a)mailman.swcp.com oix-ddp-unsubscribe(a)mailman.swcp.com To make the list name easier to remember, I have set up an email alias: oix-ddp(a)oix.org -> oix-ddp(a)mailman.swcp.com The web page for users of the OIX DDP mailing list is: https://mailman.swcp.com/cgi-bin/mailman/listinfo/oix-ddp More information can be found in our GitHub repo: https://github.com/Open-IX/BCOP Most notably: https://github.com/Open-IX/BCOP/blob/main/OIX-DDP.md The DDP itself is due for an update, and the proposed changes will be sent out to the mailing list shortly.

1 1

Whoops. .mobi whois impersonation
by Jay R. Ashworth 11 Sep '24

11 Sep '24

[ Via PRIVACY ] https://arstechnica.com/security/2024/09/rogue-whois-server-gives-researche… -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

1 0

Cloudfront Blocking IP ranges
by Brad Bendy 11 Sep '24

11 Sep '24

Does anyone know the best way to get a hold of Amazon and get out off the naughty list on Cloudfront? I've got some ranges that appear to be blocked totally by Cloudfront. Thanks in advance

2 2

Re: Re: Survey on barriers for RPKI adoption
by Lancheng 10 Sep '24

10 Sep '24

Hi Sofia, I am currently an Assistant Researcher in Zhongguancun Lab, Beijing, China. Although I am not a network operator, I am very interested in this topic. Last year, I also did a survey asking network operators about the barriers to adopting ROA and ROV. That work has been accepted by NDSS 2024 [1]. I hope this paper could be helpful. [1] https://www.ndss-symposium.org/ndss-paper/understanding-route-origin-valida… Best, Lancheng >(Apologies for duplicates) >Hello everyone, >Following up on my message below, I wanted to let everyone know that we have extended the due date for the survey on barriers to RPKI adoption until Sep 19th. >If you are a network operator who manages IP space through multiple RIRs and you haven’t already participated in the survey, please take a moment to do so as we would really appreciate having your valuable input. It will only take a few minutes: >https://www.surveymonkey.com/r/CHLHLML >At this stage, we would like to particularly encourage those of you who have not created ROAs yet to understand what barriers or challenges you have experienced, as we don’t have enough representation from this group yet. >Thanks so much in advance for your input! >Warm regards, >Sofía >-- >I am sending this email at a time that suits me and the time zone I work in. Please feel free to read, and act on or respond, at a time that suits you.

2 1