- Test - lists.nanog.org

ARIN NS down?
by Suresh Ramasubramanian 04 Feb '19

04 Feb '19

couldn't get address for 'ns1.arin.net': not found couldn't get address for 'ns2.arin.net': not found couldn't get address for 'u.arin.net': not found couldn't get address for 'ns3.arin.net': not found dig: couldn't get address for 'ns1.arin.net': no more srs@Sureshs-MacBook-Pro-2 19:56:18 <~> $ dig +trace +norec whois.arin.net ; <<>> DiG 9.10.6 <<>> +trace +norec whois.arin.net ;; global options: +cmd . 2230 IN NS m.root-servers.net. . 2230 IN NS b.root-servers.net. . 2230 IN NS c.root-servers.net. . 2230 IN NS d.root-servers.net. . 2230 IN NS e.root-servers.net. . 2230 IN NS f.root-servers.net. . 2230 IN NS g.root-servers.net. . 2230 IN NS h.root-servers.net. . 2230 IN NS i.root-servers.net. . 2230 IN NS j.root-servers.net. . 2230 IN NS a.root-servers.net. . 2230 IN NS k.root-servers.net. . 2230 IN NS l.root-servers.net. . 2230 IN RRSIG NS 8 0 518400 20190121050000 20190108040000 16749 . JqXTRb0qik0Iy1zDpwKRfKr1iZjTeiJRTk1GCfIWh9dFFvhN0c7Fiz6H lbNfhgQbPsacG0b/1I3rguS13H2guX7apppK2w88h+z8mzym2Bw1C1HR ZR3ocj/jHLJbMqHdQ+DFyRdw/AxCXBdhnbX46C8+unhQ03D/MzS0M0t4 vgadYi7BN4sa+iZIilwFV56n2dOfpzyO+evVbcnTLRZ6D4bjCHZLCtO8 EDziAPUbVAPZWiflb7/Y2dECe5gbOuGYYU/xv/Pal5+v9cjgMjcf8buG S+iTIL/lnus0JJSRDmkM6yzfYMBXC2ZqhOp+Ls+EfvmqFjIZzi394XCi pdKRZw== ;; Received 525 bytes from 10.0.0.1#53(10.0.0.1) in 40 ms net. 172800 IN NS g.gtld-servers.net. net. 172800 IN NS c.gtld-servers.net. net. 172800 IN NS j.gtld-servers.net. net. 172800 IN NS e.gtld-servers.net. net. 172800 IN NS h.gtld-servers.net. net. 172800 IN NS k.gtld-servers.net. net. 172800 IN NS m.gtld-servers.net. net. 172800 IN NS i.gtld-servers.net. net. 172800 IN NS f.gtld-servers.net. net. 172800 IN NS b.gtld-servers.net. net. 172800 IN NS a.gtld-servers.net. net. 172800 IN NS d.gtld-servers.net. net. 172800 IN NS l.gtld-servers.net. net. 86400 IN DS 35886 8 2 7862B27F5F516EBE19680444D4CE5E762981931842C465F00236401D 8BD973EE net. 86400 IN RRSIG DS 8 1 86400 20190124130000 20190111120000 16749 . uahpltN27UkKaFJRaAU1on+IpC2lpgZo84XEM7Pk7dQysKfSnqUkaVLY PXQf9kvgW5eOx/+BttQB2OWFLckJs8vv5ScOpz7dDhs8zR2FPLm93HTD 4F/XEKDNOQbFGSA3g4pZq3fatY7kFEkV9sFTH90WqJt0sXe64LYFcwr2 FtrJaS/yhEV4XDbsN3RLkBP58bf526LPpvonwSZsMUTDZcnXtUnc57ZI dlTHg2snNhVWu4qJfHDsEQPwOZagRXJhjlRT8Ox/7HwXvplmRfmeuhZb Vj5kdiY+3j0RTxpLRCG/SZRDIRcvdFKh9umdwQvAzuTS0xzO8OyPw9q8 8QCCYg== ;; Received 1171 bytes from 192.112.36.4#53(g.root-servers.net) in 207 ms arin.net. 172800 IN NS ns1.arin.net. arin.net. 172800 IN NS ns2.arin.net. arin.net. 172800 IN NS u.arin.net. arin.net. 172800 IN NS ns3.arin.net. arin.net. 86400 IN DS 48281 5 2 6EB0CCF325A8101A768C93D10CE084303D3714D4E92FEE53D6E683D2 22291017 arin.net. 86400 IN DS 48281 5 1 FCBF93357C8FE3247CECB2CD277F45EB955EE4CE arin.net. 86400 IN RRSIG DS 8 2 86400 20190117062448 20190110051448 6140 net. stuWyfC0PDuk2hNF/Bnz0lnypk+bA/slTa2KYznjmoLXDtq7v1obJq41 ZfloQKXuC7MnzpCQj70GU9ZESZq1/XU+u6wDmCqmEUbJ3kyrILxkVrln bTEySJWPmurpwUVzDVfvqFpXEOhWxOjDu6drZMcC3wG9EdPqBuFC6wlf FIQ= couldn't get address for 'ns1.arin.net': not found couldn't get address for 'ns2.arin.net': not found couldn't get address for 'u.arin.net': not found couldn't get address for 'ns3.arin.net': not found dig: couldn't get address for 'ns1.arin.net': no more

10 15

Re: [EXTERNAL] Re: RTBH no_export
by John Kristoff 04 Feb '19

04 Feb '19

On Mon, 4 Feb 2019 09:01:20 +0000 i3D.net - Martijn Schmidt <martijnschmidt(a)i3d.net> wrote: > Cogent does let you use RTBH, but on a separate BGP session to a > blackhole server. So it's a bit more hassle to set it up policy-wise, > because it deviates from the standard. Same story for "former > GlobalCrossing", now CenturyLink's AS3549, which is still used for LATAM > and Asia. There are other providers that do this besides those you listed. I'm not sure one way or the other is truly "the standard" approach, but there may be an advantage and potentially good reason to have a separate session. If a no-multihop peering link/session is down, you might still be able to establish a RTBH peering session via another path. That may be what you need to get that direct neighbor back up. :-) John

1 0

RTBH no_export
by Roel Parijs 04 Feb '19

04 Feb '19

Hello NANOG, To minimize the impact of DDoS, I have setup RTBH. For our own customers, we can set the RTBH community ourselves towards our transit suppliers and this works well. For our BGP customers the problem is more complex. Our BGP customers can send us the RTBH community, and we will drop the traffic at our borders. Since we're only running a small network, we don't have the capacity to deal with large attacks. If we would be able to forward (and maybe alter it) this RTBH community towards our upstream providers, the impact on our network would be limited. However, the RFC states that an announcement tagged with the blackhole community should get the no_advertise or no_export community. What is your opinion on this ? Thanks in advance Roel

12 13

DNS Flag Day, Friday, Feb 1st, 2019
by Brian Kantor 02 Feb '19

02 Feb '19

Quoting from the web site at https://dnsflagday.net/ What is happening? The current DNS is unnecessarily slow and suffers from inability to deploy new features. To remediate these problems, vendors of DNS software and also big public DNS providers are going to remove certain workarounds on February 1st, 2019. This change affects only sites which operate software which is not following published standards. Are you affected? On that web page, there is a Domain Owner's test. You can enter a domain name and click 'test' and shortly receive a report of what was found regarding your domain's DNS servers. I somehow managed to miss the announcement of this upcoming event, even though I read this mailing list fairly closely. Perhaps it was announced somewhere else instead. I think it needs to be mentioned here if it hasn't already been. - Brian

17 47

Weekly Routing Table Report
by cscora＠apnic.net 01 Feb '19

01 Feb '19

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 02 Feb, 2019 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 735331 Prefixes after maximum aggregation (per Origin AS): 283580 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 354621 Total ASes present in the Internet Routing Table: 63092 Prefixes per ASN: 11.65 Origin-only ASes present in the Internet Routing Table: 54357 Origin ASes announcing only one prefix: 23579 Transit ASes present in the Internet Routing Table: 8735 Transit-only ASes present in the Internet Routing Table: 268 Average AS path length visible in the Internet Routing Table: 4.2 Max AS path length visible: 31 Max AS path prepend of ASN ( 16327) 25 Prefixes from unregistered ASNs in the Routing Table: 21 Number of instances of unregistered ASNs: 23 Number of 32-bit ASNs allocated by the RIRs: 25627 Number of 32-bit ASNs visible in the Routing Table: 20862 Prefixes from 32-bit ASNs in the Routing Table: 90590 Number of bogon 32-bit ASNs visible in the Routing Table: 16 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 271 Number of addresses announced to Internet: 2842533251 Equivalent to 169 /8s, 109 /16s and 157 /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.2 Total number of prefixes smaller than registry allocations: 246362 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 200035 Total APNIC prefixes after maximum aggregation: 57413 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 197150 Unique aggregates announced from the APNIC address blocks: 81608 APNIC Region origin ASes present in the Internet Routing Table: 9414 APNIC Prefixes per ASN: 20.94 APNIC Region origin ASes announcing only one prefix: 2663 APNIC Region transit ASes present in the Internet Routing Table: 1397 Average APNIC Region AS path length visible: 4.1 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4417 Number of APNIC addresses announced to Internet: 769642274 Equivalent to 45 /8s, 223 /16s and 207 /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-139577 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: 217799 Total ARIN prefixes after maximum aggregation: 103376 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 217128 Unique aggregates announced from the ARIN address blocks: 104009 ARIN Region origin ASes present in the Internet Routing Table: 18341 ARIN Prefixes per ASN: 11.84 ARIN Region origin ASes announcing only one prefix: 6829 ARIN Region transit ASes present in the Internet Routing Table: 1851 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2562 Number of ARIN addresses announced to Internet: 1079669920 Equivalent to 64 /8s, 90 /16s and 116 /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, 45/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: 202096 Total RIPE prefixes after maximum aggregation: 96285 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 198251 Unique aggregates announced from the RIPE address blocks: 117420 RIPE Region origin ASes present in the Internet Routing Table: 25787 RIPE Prefixes per ASN: 7.69 RIPE Region origin ASes announcing only one prefix: 11488 RIPE Region transit ASes present in the Internet Routing Table: 3631 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7793 Number of RIPE addresses announced to Internet: 716711872 Equivalent to 42 /8s, 184 /16s and 39 /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: 95098 Total LACNIC prefixes after maximum aggregation: 22279 LACNIC Deaggregation factor: 4.27 Prefixes being announced from the LACNIC address blocks: 96501 Unique aggregates announced from the LACNIC address blocks: 42173 LACNIC Region origin ASes present in the Internet Routing Table: 8027 LACNIC Prefixes per ASN: 12.02 LACNIC Region origin ASes announcing only one prefix: 2174 LACNIC Region transit ASes present in the Internet Routing Table: 1505 Average LACNIC Region AS path length visible: 5.0 Max LACNIC Region AS path length visible: 31 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5577 Number of LACNIC addresses announced to Internet: 173075968 Equivalent to 10 /8s, 80 /16s and 238 /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: 20281 Total AfriNIC prefixes after maximum aggregation: 4209 AfriNIC Deaggregation factor: 4.82 Prefixes being announced from the AfriNIC address blocks: 26030 Unique aggregates announced from the AfriNIC address blocks: 9167 AfriNIC Region origin ASes present in the Internet Routing Table: 1239 AfriNIC Prefixes per ASN: 21.01 AfriNIC Region origin ASes announcing only one prefix: 425 AfriNIC Region transit ASes present in the Internet Routing Table: 246 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 513 Number of AfriNIC addresses announced to Internet: 103031296 Equivalent to 6 /8s, 36 /16s and 34 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/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 4538 4653 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4579 531 527 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 3056 1241 49 VIETEL-AS-AP Viettel Group, VN 45899 3006 1725 112 VNPT-AS-VN VNPT Corp, VN 4766 2811 11127 767 KIXS-AS-KR Korea Telecom, KR 9829 2752 1496 551 BSNL-NIB National Internet Backbone, IN 9808 2437 8699 26 CMNET-GD Guangdong Mobile Communication 9394 2395 4906 29 CTTNET China TieTong Telecommunications 4755 2142 438 183 TATACOMM-AS TATA Communications formerl 17974 2034 968 50 TELKOMNET-AS2-AP PT Telekomunikasi Indo 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 6327 3578 1326 92 SHAW - Shaw Communications Inc., CA 11492 3495 226 595 CABLEONE - CABLE ONE, INC., US 22773 3310 2979 174 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2598 5391 1021 AMAZON-02 - Amazon.com, Inc., US 16625 2275 1250 1715 AKAMAI-AS - Akamai Technologies, Inc., 20115 2152 2759 536 CHARTER-20115 - Charter Communications, 18566 2136 405 108 MEGAPATH5-US - MegaPath Corporation, US 5650 2089 3074 1462 FRONTIER-FRTR - Frontier Communications 30036 2078 345 292 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 2068 5076 577 CENTURYLINK-US-LEGACY-QWEST - CenturyLi 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 5329 1628 138 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3273 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2631 560 1915 AKAMAI-ASN1, US 12389 2205 2209 657 ROSTELECOM-AS, RU 34984 2066 339 527 TELLCOM-AS, TR 9121 1682 1691 17 TTNET, TR 13188 1605 100 46 TRIOLAN, UA 9009 1327 145 741 M247, GB 8402 1316 545 15 CORBINA-AS OJSC "Vimpelcom", RU 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 5546 3325 589 Uninet S.A. de C.V., MX 10620 2959 448 993 Telmex Colombia S.A., CO 11830 2683 371 60 Instituto Costarricense de Electricidad 6503 1565 449 55 Axtel, S.A.B. de C.V., MX 7303 1409 934 221 Telecom Argentina S.A., AR 6147 1286 377 29 Telefonica del Peru S.A.A., PE 28573 1173 2240 183 CLARO S.A., BR 3816 1029 511 115 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 931 143 66 Alestra, S. de R.L. de C.V., MX 13999 911 528 243 Mega Cable, S.A. 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 1152 393 21 LINKdotNET-AS, EG 37611 907 107 9 Afrihost, ZA 36903 797 401 142 MT-MPLS, MA 36992 789 1411 44 ETISALAT-MISR, EG 24835 685 636 22 RAYA-AS, EG 8452 640 1731 20 TE-AS TE-AS, EG 29571 485 70 13 ORANGE-COTE-IVOIRE, CI 37492 468 470 57 ORANGE-, TN 15399 425 45 11 WANANCHI-, KE 37342 419 32 1 MOVITEL, MZ 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 5546 3325 589 Uninet S.A. de C.V., MX 12479 5329 1628 138 UNI2-AS, ES 4538 4653 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4579 531 527 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 6327 3578 1326 92 SHAW - Shaw Communications Inc., CA 11492 3495 226 595 CABLEONE - CABLE ONE, INC., US 22773 3310 2979 174 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 8551 3273 378 43 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 7552 3056 1241 49 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 12479 5329 5191 UNI2-AS, ES 4538 4653 4579 ERX-CERNET-BKB China Education and Research Net 7545 4579 4052 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3578 3486 SHAW - Shaw Communications Inc., CA 8551 3273 3230 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 3310 3136 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 3056 3007 VIETEL-AS-AP Viettel Group, VN 11492 3495 2900 CABLEONE - CABLE ONE, INC., US 45899 3006 2894 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 64339 UNALLOCATED 143.0.108.0/22 18747 IFX18747 - IFX Corporation, US 64355 UNALLOCATED 156.40.196.0/24 30387 NIH-NET-NCCS - National Instit 64011 UNALLOCATED 166.133.128.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.133.192.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.184.9.0/24 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.220.64.0/19 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.220.96.0/19 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64141 UNALLOCATED 181.119.152.0/24 264619 Wireless Provider, AR Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.171.96.0/24 394378 NMICA-01 - NMICA, LLC, US 27.100.7.0/24 56096 UNKNOWN 27.126.156.0/22 55827 UNKNOWN 27.126.156.0/23 55827 UNKNOWN 27.126.158.0/23 55827 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.255.80.0/24 36351 SOFTLAYER - SoftLayer Technologies Inc., US 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:12 /9:10 /10:36 /11:99 /12:292 /13:568 /14:1129 /15:1918 /16:13373 /17:7882 /18:13853 /19:25609 /20:39703 /21:46133 /22:91481 /23:74783 /24:415615 /25:924 /26:820 /27:864 /28:20 /29:6 /30:7 /31:0 /32:194 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 4179 5329 UNI2-AS, ES 6327 3340 3578 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2757 3495 CABLEONE - CABLE ONE, INC., US 8551 2729 3273 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2550 3310 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2031 2136 MEGAPATH5-US - MegaPath Corporation, US 11830 2029 2683 Instituto Costarricense de Electricidad y Telec 30036 1826 2078 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 5650 1761 2089 FRONTIER-FRTR - Frontier Communications of Amer Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1612 2:896 4:23 5:2786 6:47 7:1 8:1176 12:1867 13:315 14:1867 15:37 16:2 17:219 18:57 20:50 23:2604 24:2481 25:2 27:2544 31:2043 32:94 35:35 36:831 37:3016 38:1616 39:294 40:122 41:3127 42:726 43:2003 44:141 45:6567 46:3223 47:248 49:1344 50:1080 51:319 52:1078 54:347 55:1 56:6 57:41 58:1705 59:1054 60:481 61:2056 62:2075 63:1794 64:5076 65:2195 66:4826 67:2693 68:1172 69:3485 70:1150 71:603 72:2288 74:2758 75:418 76:544 77:1730 78:1762 79:2314 80:1641 81:1423 82:1103 83:897 84:1084 85:2140 86:560 87:1554 88:990 89:2414 90:215 91:6569 92:1239 93:2434 94:2482 95:3232 96:919 97:349 98:944 99:169 100:87 101:1160 102:373 103:19926 104:3562 105:249 106:867 107:1812 108:693 109:3672 110:1611 111:1865 112:1389 113:1409 114:1148 115:1722 116:1671 117:1919 118:2190 119:1621 120:1046 121:1030 122:2366 123:1644 124:1454 125:1950 128:1206 129:675 130:523 131:1646 132:713 133:218 134:1046 135:238 136:550 137:681 138:1959 139:835 140:570 141:803 142:801 143:1008 144:891 145:505 146:1248 147:802 148:1713 149:794 150:782 151:1005 152:1005 153:324 154:2446 155:966 156:1650 157:892 158:657 159:1919 160:1512 161:910 162:2671 163:780 164:1135 165:1573 166:438 167:1384 168:3263 169:869 170:4013 171:526 172:1090 173:2157 174:999 175:883 176:2301 177:3997 178:2559 179:1292 180:2090 181:2440 182:2680 183:1049 184:1149 185:14683 186:3707 187:2452 188:2894 189:2008 190:8343 191:1454 192:10068 193:6538 194:5335 195:4044 196:2973 197:1736 198:5789 199:5973 200:7273 201:5104 202:10104 203:10152 204:4619 205:3005 206:3318 207:3274 208:3959 209:4228 210:3939 211:1986 212:3063 213:2837 214:1082 215:52 216:5978 217:2199 218:919 219:574 220:1845 221:995 222:994 223:1427 End of report

1 0

RapidScale Network Contact
by Nathanael Catangay Cariaga 01 Feb '19

01 Feb '19

Good day to all. I would like to reach out to any Rapid Scale network contact on this list. Have some few clarifications on the latency spike within the RapidScale network when doing traceroutes going to some IPs. Thanks in advance. -nathan

1 0

RPKI Documentation as an open source project
by Alex Band 01 Feb '19

01 Feb '19

Hey all, A couple on months ago we started putting together an FAQ on RPKI [0] which led to quite a number of community contributions. We decided to expand upon this project and write comprehensive RPKI documentation, as an open source project. Other than reading every RFC on the topic, this should give operators a good understanding of the moving parts involved, and how to use RPKI in the real world. We got to the point where we think we have all the basics covered and made it available here: https://rpki.readthedocs.io As this is a project on GitHub [1] and managed using the Sphinx documentation tooling, we welcome corrections, additions, readability improvements and even translations. Feel free to create an issue or pull request on GitHub. Hope this is useful! See y’all in S.F. Cheers, Martin, Tim & Alex The NLnet Labs RPKI Team [0] https://github.com/NLnetLabs/rpki-faq [1] https://github.com/NLnetLabs/rpki-doc

1 0

Google you have a problem.
by Mark Andrews 01 Feb '19

01 Feb '19

[beetle:~/git/bind9] marka% fetch -v https://www.google.com/jsapi looking up www.google.com connecting to www.google.com:443 SSL connection established using ECDHE-RSA-AES128-GCM-SHA256 Certificate subject: /C=US/ST=California/L=Mountain View/O=Google LLC/CN=www.google.com Certificate issuer: /C=US/O=Google Trust Services/CN=Google Internet Authority G3 requesting https://www.google.com/jsapi fetch: https://www.google.com/jsapi: Bad Gateway [beetle:~/git/bind9] marka% curl -v https://www.google.com/jsapi * Trying 2607:f8b0:4007:80e::2004... * TCP_NODELAY set * Trying 172.217.14.100... * TCP_NODELAY set * Connected to www.google.com (2607:f8b0:4007:80e::2004) port 443 (#0) * ALPN, offering http/1.1 * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH * successfully set certificate verify locations: * CAfile: /opt/local/share/curl/curl-ca-bundle.crt CApath: none * TLSv1.2 (OUT), TLS header, Certificate Status (22): * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS change cipher, Change cipher spec (1): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256 * ALPN, server accepted to use http/1.1 * Server certificate: * subject: C=US; ST=California; L=Mountain View; O=Google LLC; CN=www.google.com * start date: Jan 15 13:15:00 2019 GMT * expire date: Apr 9 13:15:00 2019 GMT * subjectAltName: host "www.google.com" matched cert's "www.google.com" * issuer: C=US; O=Google Trust Services; CN=Google Internet Authority G3 * SSL certificate verify ok. > GET /jsapi HTTP/1.1 > Host: www.google.com > User-Agent: curl/7.63.0 > Accept: */* > < HTTP/1.1 502 Bad Gateway < Content-Length: 0 < Date: Thu, 31 Jan 2019 22:20:34 GMT < Content-Type: text/html; charset=UTF-8 < Alt-Svc: quic=":443"; ma=2592000; v="44,43,39" < * Connection #0 to host www.google.com left intact [beetle:~/git/bind9] marka% curl -4 -v https://www.google.com/jsapi * Trying 172.217.14.100... * TCP_NODELAY set * Connected to www.google.com (172.217.14.100) port 443 (#0) * ALPN, offering http/1.1 * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH * successfully set certificate verify locations: * CAfile: /opt/local/share/curl/curl-ca-bundle.crt CApath: none * TLSv1.2 (OUT), TLS header, Certificate Status (22): * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS change cipher, Change cipher spec (1): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256 * ALPN, server accepted to use http/1.1 * Server certificate: * subject: C=US; ST=California; L=Mountain View; O=Google LLC; CN=www.google.com * start date: Jan 15 13:15:00 2019 GMT * expire date: Apr 9 13:15:00 2019 GMT * subjectAltName: host "www.google.com" matched cert's "www.google.com" * issuer: C=US; O=Google Trust Services; CN=Google Internet Authority G3 * SSL certificate verify ok. > GET /jsapi HTTP/1.1 > Host: www.google.com > User-Agent: curl/7.63.0 > Accept: */* > < HTTP/1.1 502 Bad Gateway < Content-Length: 0 < Date: Thu, 31 Jan 2019 22:24:43 GMT < Content-Type: text/html; charset=UTF-8 < Alt-Svc: quic=":443"; ma=2592000; v="44,43,39" < * Connection #0 to host www.google.com left intact [beetle:~/git/bind9] marka% traceroute 172.217.14.100 traceroute to 172.217.14.100 (172.217.14.100), 64 hops max, 52 byte packets 1 172.30.42.65 (172.30.42.65) 1.340 ms 3.278 ms 1.673 ms 2 * * * 3 * * * 4 59.154.18.232 (59.154.18.232) 13.710 ms hu0-5-0-0.22btpr01.optus.net.au (59.154.18.234) 24.311 ms 13.662 ms 5 72.14.219.128 (72.14.219.128) 12.445 ms 43.781 ms 10.760 ms 6 108.170.247.74 (108.170.247.74) 12.743 ms 12.797 ms 108.170.247.59 (108.170.247.59) 14.167 ms 7 216.239.50.172 (216.239.50.172) 159.864 ms 162.324 ms 157.546 ms 8 108.170.230.130 (108.170.230.130) 147.234 ms 151.094 ms 152.088 ms 9 108.170.247.129 (108.170.247.129) 152.073 ms 149.194 ms 149.055 ms 10 108.170.230.137 (108.170.230.137) 149.697 ms 150.042 ms 74.125.252.75 (74.125.252.75) 149.363 ms 11 lax31s01-in-f4.1e100.net (172.217.14.100) 158.438 ms 147.982 ms 149.593 ms [beetle:~/git/bind9] marka% -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org

2 5

Re: Waves between Buffalo and Manhattan
by Rob Wcislo 31 Jan '19

31 Jan '19

GTT has this route via legacy Hibernia [Image] Rob Wcislo VP, Sales GTT (954)305-2289 On Thu, Jan 31, 2019 at 11:00 AM -0500, wrote: GTT can sell waves between Buffalo-NYC bypassing Albany via Newark. From: NANOG <nanog-bounces(a)nanog.org> On Behalf Of Tom Beecher Sent: Friday, January 18, 2019 3:58 PM To: NANOG Mailing List <nanog(a)nanog.org> Subject: Re: Waves between Buffalo and Manhattan If it's for the use case I suspect it would be for, Firstlight and Windstream should bring you closer to where you'll want to be on the Buffalo side. On Fri, Jan 18, 2019 at 1:38 PM Benjamin Hatton <bhatton(a)htva.net<mailto:bhatton@htva.net>> wrote: The regional players in the area that may have something that would bypass Albany would be Firstlight (Formerly Finger Lakes Technology Group) and Uniti. Firstlight has more fiber in the area, and would be my choice over Uniti, I have services with both. Contact me off list if you want an introduction to a sales guy. On Fri, Jan 18, 2019 at 1:00 PM Mehmet Akcin <mehmet(a)akcin.net<mailto:mehmet@akcin.net>> wrote: hi Jason https://dev.networkatlas.org<https://url.emailprotection.link/?a-r1D0y9U1MOQhiHHdIdbG_R7A0sKCid4QH4OqBWz…> shows Zayo, Windstream (and Earthlink) there. We are working with Charter , Level3/CL to load their fiber routes , but it will be there and you will be able to connect with the sales teams directly by clicking on a route. . In addition to that there are other small players in this region. Mehmet On Fri, Jan 18, 2019 at 9:49 AM Jason Lixfeld <jason+nanog(a)lixfeld.ca<mailto:jason%2Bnanog@lixfeld.ca>> wrote: Hello, Does anyone have knowledge of carriers who are able to deliver 10G or 100G waves between Buffalo and Manhattan that *do not* touch Albany? I know Zayo is one. I’m waiting to hear back from CenturyLink. I’ve reviewed networkatlas.org<https://url.emailprotection.link/?a1AgcS990NxBSGfMW_Ik8M_uM9FRuu3jqLwqpqIvy…>, to see if anything pops up there, but otherwise I’m coming up empty. Thanks in advance.

1 0

Effects of Cold Front on Internet Infrastructure - U.S. Midwest
by Mark Tinka 31 Jan '19

31 Jan '19

For anyone running IP networks in the Midwest, are you having to do anything special to keep your networks up? For the data centres, is this cold front a chance to reduce air conditioning costs, or is it actually straining the infrastructure? I'm curious, from a +27-degree C summer's day here in Johannesburg. Mark.

12 20