- Test - lists.nanog.org

Fiber across SF Bay
by Ben Cannon 02 May '20

02 May '20

Does anyone have recommendations for dark fiber or a full 432 across the SF bay bridge? -Ben

1 0

Huawei on Mount Everest
by Glen Kent 02 May '20

02 May '20

https://telecoms.com/504051/huawei-and-china-mobile-stick-a-5g-base-station… Why dont we leave the Everest alone? OTOH, we can now have tiktok videos and latest instagram posts from the summit. Yippe. Just when you think things cant get worse, they sink deeper.

10 9

LTE modem where I can control the MTU
by Dovid Bender 02 May '20

02 May '20

Hi, We have VZ wireless in the data center as a backup to our core infrastructure. We have an issue where if packets have a large MTU they seem to die. Does anyone know of a good 4G modem where I can set the MTU on the cellular connection? TIA. Dovid

5 6

Weekly Routing Table Report
by cscora＠apnic.net 01 May '20

01 May '20

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 02 May, 2020 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 808187 Prefixes after maximum aggregation (per Origin AS): 307501 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 395431 Total ASes present in the Internet Routing Table: 67932 Prefixes per ASN: 11.90 Origin-only ASes present in the Internet Routing Table: 58336 Origin ASes announcing only one prefix: 24318 Transit ASes present in the Internet Routing Table: 9596 Transit-only ASes present in the Internet Routing Table: 308 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 50 Max AS path prepend of ASN ( 22394) 38 Prefixes from unregistered ASNs in the Routing Table: 1118 Number of instances of unregistered ASNs: 1120 Number of 32-bit ASNs allocated by the RIRs: 31477 Number of 32-bit ASNs visible in the Routing Table: 26018 Prefixes from 32-bit ASNs in the Routing Table: 120094 Number of bogon 32-bit ASNs visible in the Routing Table: 22 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 0 Number of addresses announced to Internet: 2841688576 Equivalent to 169 /8s, 96 /16s and 186 /24s Percentage of available address space announced: 76.8 Percentage of allocated address space announced: 76.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 600761 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 212345 Total APNIC prefixes after maximum aggregation: 62309 APNIC Deaggregation factor: 3.41 Prefixes being announced from the APNIC address blocks: 0 Unique aggregates announced from the APNIC address blocks: 0 APNIC Region origin ASes present in the Internet Routing Table: 10545 APNIC Prefixes per ASN: 0.00 APNIC Region origin ASes announcing only one prefix: 2935 APNIC Region transit ASes present in the Internet Routing Table: 1578 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 27 Number of APNIC region 32-bit ASNs visible in the Routing Table: 5615 Number of APNIC addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /24s APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-141625 APNIC Address Blocks ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 236903 Total ARIN prefixes after maximum aggregation: 108901 ARIN Deaggregation factor: 2.18 Prefixes being announced from the ARIN address blocks: 0 Unique aggregates announced from the ARIN address blocks: 0 ARIN Region origin ASes present in the Internet Routing Table: 18475 ARIN Prefixes per ASN: 0.00 ARIN Region origin ASes announcing only one prefix: 6734 ARIN Region transit ASes present in the Internet Routing Table: 1909 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 42 Number of ARIN region 32-bit ASNs visible in the Routing Table: 3222 Number of ARIN addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /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 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 229537 Total RIPE prefixes after maximum aggregation: 106163 RIPE Deaggregation factor: 2.16 Prefixes being announced from the RIPE address blocks: 0 Unique aggregates announced from the RIPE address blocks: 0 RIPE Region origin ASes present in the Internet Routing Table: 27049 RIPE Prefixes per ASN: 0.00 RIPE Region origin ASes announcing only one prefix: 11730 RIPE Region transit ASes present in the Internet Routing Table: 3833 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 31 Number of RIPE region 32-bit ASNs visible in the Routing Table: 9137 Number of RIPE addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /24s RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 64396-64495 196608-213403 RIPE Address Blocks LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 105959 Total LACNIC prefixes after maximum aggregation: 24678 LACNIC Deaggregation factor: 4.29 Prefixes being announced from the LACNIC address blocks: 0 Unique aggregates announced from the LACNIC address blocks: 0 LACNIC Region origin ASes present in the Internet Routing Table: 9793 LACNIC Prefixes per ASN: 0.00 LACNIC Region origin ASes announcing only one prefix: 2434 LACNIC Region transit ASes present in the Internet Routing Table: 1850 Average LACNIC Region AS path length visible: 5.1 Max LACNIC Region AS path length visible: 50 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 7368 Number of LACNIC addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + ERX transfers LACNIC Address Blocks AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 22324 Total AfriNIC prefixes after maximum aggregation: 4721 AfriNIC Deaggregation factor: 4.73 Prefixes being announced from the AfriNIC address blocks: 0 Unique aggregates announced from the AfriNIC address blocks: 0 AfriNIC Region origin ASes present in the Internet Routing Table: 1387 AfriNIC Prefixes per ASN: 0.00 AfriNIC Region origin ASes announcing only one prefix: 485 AfriNIC Region transit ASes present in the Internet Routing Table: 269 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 23 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 676 Number of AfriNIC addresses announced to Internet: 0 Equivalent to 0 /8s, 0 /16s and 0 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & ERX transfers AfriNIC Address Blocks APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7545 5444 686 635 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4739 4192 73 ERX-CERNET-BKB China Education and Rese 7552 3409 1330 22 VIETEL-AS-AP Viettel Group, VN 45899 2810 1765 152 VNPT-AS-VN VNPT Corp, VN 7713 2709 830 512 TELKOMNET-AS-AP PT Telekomunikasi Indon 9808 2561 9043 62 CMNET-GD Guangdong Mobile Communication 4766 2267 11102 561 KIXS-AS-KR Korea Telecom, KR 9498 2264 434 221 BBIL-AP BHARTI Airtel Ltd., IN 4755 2124 441 194 TATACOMM-AS TATA Communications formerl 9394 2042 4914 20 CTTNET China TieTong Telecommunications Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 11492 4286 287 666 CABLEONE, US 7155 4034 280 28 VIASAT-SP-BACKBONE, US 16509 4017 7879 1786 AMAZON-02, US 22773 3532 2968 149 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3364 1324 92 SHAW, CA 16625 3053 1593 2185 AKAMAI-AS, US 209 2406 5077 541 CENTURYLINK-US-LEGACY-QWEST, US 30036 2389 365 94 MEDIACOM-ENTERPRISE-BUSINESS, US 5650 2301 2981 1621 FRONTIER-FRTR, US 26484 2194 137 175 IKGUL-26484, US Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 5769 1603 138 UNI2-AS, ES 31334 4768 484 13 KABELDEUTSCHLAND-AS, DE 39891 3409 193 22 ALJAWWALSTC-AS, SA 8551 3201 379 45 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2968 454 2030 AKAMAI-ASN1, EU 12389 2495 2251 725 ROSTELECOM-AS, RU 9009 2166 228 1179 M247, GB 34984 2052 350 559 TELLCOM-AS, TR 9121 1901 1691 18 TTNET, TR 13188 1606 100 36 TRIOLAN, UA Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6537 3317 598 Uninet S.A. de C.V., MX 10620 3348 529 533 Telmex Colombia S.A., CO 11830 2671 369 63 Instituto Costarricense de Electricidad 6503 1689 327 387 Axtel, S.A.B. de C.V., MX 7303 1552 1031 262 Telecom Argentina S.A., AR 13999 1375 506 333 Mega Cable, S.A. de C.V., MX 28573 1374 2242 203 CLARO S.A., BR 6147 1145 379 39 Telefonica del Peru S.A.A., PE 3816 1097 570 141 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 957 112 70 Alestra, S. de R.L. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1391 393 22 LINKdotNET-AS, EG 24835 1106 574 25 RAYA-AS, EG 36992 1091 1539 76 ETISALAT-MISR, EG 36903 890 467 88 MT-MPLS, MA 29571 600 68 12 ORANGE-COTE-IVOIRE, CI 6713 561 1863 34 IAM-AS, MA 37342 466 32 1 MOVITEL, MZ 36935 407 522 44 Vodafone-, EG 23889 365 231 15 MauritiusTelecom, MU 15399 349 45 10 WANANCHI-, KE Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 6537 3317 598 Uninet S.A. de C.V., MX 12479 5769 1603 138 UNI2-AS, ES 7545 5444 686 635 TPG-INTERNET-AP TPG Telecom Limited, AU 31334 4768 484 13 KABELDEUTSCHLAND-AS, DE 4538 4739 4192 73 ERX-CERNET-BKB China Education and Rese 11492 4286 287 666 CABLEONE, US 7155 4034 280 28 VIASAT-SP-BACKBONE, US 16509 4017 7879 1786 AMAZON-02, US 22773 3532 2968 149 ASN-CXA-ALL-CCI-22773-RDC, US 7552 3409 1330 22 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 12479 5769 5631 UNI2-AS, ES 7545 5444 4809 TPG-INTERNET-AP TPG Telecom Limited, AU 31334 4768 4755 KABELDEUTSCHLAND-AS, DE 4538 4739 4666 ERX-CERNET-BKB China Education and Research Net 7155 4034 4006 VIASAT-SP-BACKBONE, US 11492 4286 3620 CABLEONE, US 7552 3409 3387 VIETEL-AS-AP Viettel Group, VN 39891 3409 3387 ALJAWWALSTC-AS, SA 22773 3532 3383 ASN-CXA-ALL-CCI-22773-RDC, US 6327 3364 3272 SHAW, CA Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 174 COGENT-174, US 62485 UNALLOCATED 8.23.229.0/24 3356 LEVEL3, US 32985 UNALLOCATED 8.28.31.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 174 COGENT-174, US 14109 UNALLOCATED 8.38.252.0/24 3356 LEVEL3, US 23061 UNALLOCATED 8.39.119.0/24 3356 LEVEL3, US 26584 UNALLOCATED 8.42.62.0/23 209 CENTURYLINK-US-LEGACY-QWEST, 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 40544 UNALLOCATED 12.0.33.0/24 6461 ZAYO-6461, US Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at http://thyme.rand.apnic.net/current/data-dsua Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:9 /9:11 /10:38 /11:99 /12:286 /13:577 /14:1168 /15:1917 /16:13366 /17:8219 /18:13618 /19:25839 /20:40628 /21:48099 /22:100080 /23:82727 /24:470239 /25:1267 /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 5610 5769 UNI2-AS, ES 8151 5146 6537 Uninet S.A. de C.V., MX 31334 4757 4768 KABELDEUTSCHLAND-AS, DE 11492 4040 4286 CABLEONE, US 7155 3900 4034 VIASAT-SP-BACKBONE, US 16509 3889 4017 AMAZON-02, US 7545 3434 5444 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3423 3532 ASN-CXA-ALL-CCI-22773-RDC, US 39891 3409 3409 ALJAWWALSTC-AS, SA 7552 3299 3409 VIETEL-AS-AP Viettel Group, VN Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1590 2:1155 3:30 4:19 5:3351 6:51 8:1408 9:1 11:1 12:1795 13:506 14:2289 15:75 16:9 17:296 18:81 20:84 23:3531 24:2265 25:2 27:2551 31:3101 32:104 34:3 35:43 36:922 37:3269 38:1965 39:391 40:124 41:3573 42:675 43:2115 44:202 45:14260 46:3703 47:286 49:1449 50:1419 51:91 52:1105 54:264 55:656 56:6 57:52 58:1768 59:1171 60:726 61:2278 62:2201 63:1980 64:5119 65:2297 66:4933 67:2831 68:1193 69:3844 70:1430 71:678 72:2891 74:2604 75:1434 76:682 77:2818 78:1870 79:2420 80:1910 81:1636 82:1267 83:1166 84:1205 85:2548 86:550 87:1704 88:1146 89:2753 90:314 91:7890 92:1502 93:2314 94:2665 95:3986 96:1141 97:333 98:933 99:976 100:87 101:970 102:891 103:23638 104:3456 105:379 106:808 107:1982 108:701 109:3667 110:1849 111:1998 112:1605 113:1392 114:1549 115:1829 116:1791 117:2081 118:2116 119:1729 120:820 121:1049 122:2437 123:1993 124:1570 125:2035 128:1348 129:1205 130:635 131:1831 132:765 133:300 134:1307 135:291 136:613 137:853 138:2157 139:992 140:644 141:942 142:910 143:1200 144:976 145:331 146:1494 147:1042 148:2100 149:1179 150:859 151:1299 152:1493 153:383 154:4739 155:1050 156:3392 157:1102 158:833 159:1972 160:1924 161:1042 162:3054 163:855 164:1453 165:1284 166:532 167:1631 168:3459 169:527 170:4207 171:769 172:1929 173:2526 174:1007 175:1018 176:2625 177:4213 178:3049 179:1514 180:2319 181:2526 182:3082 183:1127 184:2415 185:16404 186:3754 187:2728 188:4106 189:2278 190:8620 191:1433 192:10367 193:7469 194:6113 195:4392 196:3209 197:1874 198:6088 199:5968 200:7213 201:5208 202:10508 203:10189 204:4530 205:3096 206:3238 207:3296 208:4044 209:4430 210:4004 211:2015 212:3329 213:3077 214:1167 215:61 216:5969 217:2407 218:899 219:611 220:2035 221:915 222:1007 223:1467 End of report

1 0

BT static routing to CPE
by Tom Ammon 01 May '20

01 May '20

Hi All, I've inherited a circuit that can't be replaced, on which I need to get some services working, from BT in the UK. The sales people are saying that they can't give me an additional PA IPv4 block (static routed behind the CPE->PE link), that the only option for expanding the addressing is to increase the size of the subnet on the link. Does anyone here know better, and if so, could you point me to someone at BT who could help get an additional PA block allocated for us? Tom -- ----------------------------------------------------------------------------- Tom Ammon M: (801) 784-2628 thomasammon(a)gmail.com -----------------------------------------------------------------------------

3 3

dot-org TLD sale halted by ICANN
by Andy Ringsmuth 01 May '20

01 May '20

https://www.theregister.co.uk/2020/05/01/icann_stops_dot_org_sale/ I know this has been bantered about on the list in the past. Great (IMHO) to see this happen. ---- Andy Ringsmuth 5609 Harding Drive Lincoln, NE 68521-5831 (402) 304-0083 andy(a)andyring.com “Better even die free, than to live slaves.” - Frederick Douglas, 1863

5 6

mail admins?
by William Herrin 01 May '20

01 May '20

Howdy,, How do we contact the nanog mail admins? I looked at https://archive.nanog.org/list and https://archive.nanog.org/list/faq but apparently someone thought it'd be clever to redact all the email addresses from that page. "Questions should be directed to[email protected]." Thanks, Bill Herrin -- William Herrin bill(a)herrin.us https://bill.herrin.us/

12 16

Google peering pains in Dallas
by Kaiser, Erich 30 Apr '20

30 Apr '20

So it has been 3 weeks of major ICMP packet loss to any google service over the Dallas Equinix IX, it is not affecting performance of service but is affecting us with customer complaints and service calls due to some software using it for monitoring purposes people using it for benchmark testing. I have been told from them that they know the cause now and know that a Large ISP on the IX is causing the issue(Hmm wonder who that is...), so why do they not shutdown the peer with them and force the ISP to fix the issue? This issue is affecting everyone on the IX not just us, very very frustrating. Hopefully this will reach someone over there that can do something about it..... Erich Kaiser The Fusion Network erich(a)gotfusion.net

10 11

Abuse Desks
by Mike Hammett 30 Apr '20

30 Apr '20

I noticed over the weekend that a Fail2Ban instance's complain function wasn't working. I fixed it. I've noticed a few things: 1) Abusix likes to return RIR abuse contact information. The vast majority are LACNIC, but it also has kicked back a couple for APNIC and ARIN. When I look up the compromised IP address in Abusix via the CLI, the APNIC and ARIN ones return both ISP contact information and RIR information. When I look them up on the RIR's whois, it just shows the ISP abuse information. Weird, but so rare it's probably just an anomaly. However, almost everything I see in LACNIC's region is returned with only the LACNIC abuse information when the ones I've checked on LACNIC's whois list valid abuse information for that prefix. Can anyone confirm they've seen similar behavior out of Abusix? I reached out to them, but haven't heard back. 2) Digital Ocean hits my radar far more than any other entity. 3) Azure shows up a lot less than GCP or AWS, which are about similar to each other. 4) Around 5% respond saying it's been addressed (or why it's not in the event of security researchers) within a couple hours. The rest I don't know. I've had a mix of small and large entities in that response. 5) HostGator seems to have an autoresponder (due to a 1 minute response) that just indicates that you sent nothing actionable, despite the report including the relevant log file entries. 6) Charter seems to have someone actually looking at it as it took them 16 - 17 hours to respond, but they say they don't have enough information to act on, requesting relevant log file entries... which were provided in the initial report and are even included in their response. They request relevant log file entries with the date, time, timezone, etc. all in the body in plain text, which was delivered. 7) The LACNIC region has about 1/3 of my reports. Do these mirror others' observations with security issues and how abuse desks respond? ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

26 58

Re: Abuse Desks
by Hal Murray 30 Apr '20

30 Apr '20

Mike Hammett said: > IMO, the answer is balance. > - Handful of SSH connection attempts against a server. Nobody got in, > security hardening did it's job. I don't think that is worth reporting. - > Constant brute force SSH attempts from a given source over an extended period > of time, or a clear pattern of probing, yes, report that. The bad guys have already gamed that system. If you have a zillion bots, you can have each bot try a different name/password on a large batch of IP Addresses. A victim only sees one try from each bot. The daily logwatch reports that land in my mailbox are full of ssh attempts that end with ": 1 Time". ----------- Matt Corallo said: > I'm open to ideas on what to do here, but the abuse system as it exists today > is clearly broken for me, and its clearly broken for AWS/GCP/Azure/OVH/etc - > have you ever tried emailing their registered abuse contacts? I have, the > problem doesn't go away and there are no responses. > especially given most of the real crap out there comes from hosting providers > like the above who don't have the bandwidth to respond. "don't have the bandwidth" is an interesting term. Is that because the problem is really hard and it would take a lot of bandwidth/money/whatever, or because they choose not to spend money on it and the rest of the net is letting them get away with it? ---------- Tom Beecher said: > Abuse departments should be properly handling LEGITIMATE abuse complaints. > Not crufty background noise traffic that is never going away. Agreed. But the abuse desk is the only place where somebody can find the signal in the noise, and with the current pattern, much of the signal is trying to hide in the noise. The abuse desk will only see the signal if people actually send in abuse reports and the abuse desk actually looks at them. ---------- Laszlo Hanyecz said: > A lot of this other stuff is just people abusing the abuse contacts to get > someone else taken offline. Phishing websites fall into this category - > it's not network abuse, it's just content someone doesn't like, and one way > to get it taken down is to threaten the network that carries the traffic for > it. I don't report phishing websites unless somebody spams me with the URL. -- These are my opinions. I hate spam.

2 1