- NANOG - lists.nanog.org

is something weird going on with cox, level3, and/or cogent
by Miles Fidelman 13 Feb '17

13 Feb '17

Hi Folks, I'm visiting AZ, and seeing some really really poor performance accessing some of our servers via Cox broadband. The folks at Cox technical support are useless - all they say is "well you're on a DOCSIS 2 modem." Meanwhile, everything I'm seeing is several hops upstream of the local segment - and all that Cox level2 tech support will say is "if there was a backbone problem, our backbone people would have dealt with it." I'm having problems reaching both our own server, and sites like google, facebook, windows update. Traceroutes to and from our server are illustrative - note that for most of the past week, the average ping time was 85msec. Now we're seeing this: From 98.177.135.186 - the public IP address on Cox's local broadband service. To 107.154.13.58 (ntcorp.server - one of our servers, sitting in a Tierpoint data center, near Boston) traceroute to ntcorp.com (207.154.13.58), 64 hops max, 52 byte packets 1 10.128.128.1 (10.128.128.1) 199.893 ms 75.319 ms 27.295 ms 2 100.127.69.178 (100.127.69.178) 38.710 ms 40.075 ms 43.598 ms 3 72.215.229.22 (72.215.229.22) 39.674 ms 201.368 ms * 4 lag-157.bear2.phoenix1.level3.net (4.28.82.53) 686.499 ms 1837.141 ms 16.273 ms 5 ae-1-60.edge1.losangeles6.level3.net (4.69.144.16) 35.498 ms 964.377 ms * 6 ae-3-80.edge1.losangeles6.level3.net (4.69.144.144) 551.760 ms 525.014 ms ae-1-60.edge1.losangeles6.level3.net (4.69.144.16) 2061.191 ms 7 be3036.ccr41.lax04.atlas.cogentco.com (154.54.14.129) 847.778 ms 87.601 ms 71.504 ms 8 be2965.ccr22.lax01.atlas.cogentco.com (154.54.45.1) 79.060 ms 225.647 ms be2964.ccr21.lax01.atlas.cogentco.com (154.54.44.77) 60.306 ms 9 * be2931.ccr21.phx02.atlas.cogentco.com (154.54.44.85) 2264.071 ms 185.180 ms 10 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 61.208 ms be2930.ccr21.elp01.atlas.cogentco.com (154.54.42.78) 386.149 ms 1278.868 ms 11 be2928.ccr22.iah01.atlas.cogentco.com (154.54.30.161) 384.136 ms be2927.ccr41.iah01.atlas.cogentco.com (154.54.29.221) 2339.833 ms 615.415 ms 12 be2690.ccr42.atl01.atlas.cogentco.com (154.54.28.129) 233.061 ms be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 87.902 ms be2690.ccr42.atl01.atlas.cogentco.com (154.54.28.129) 861.159 ms 13 be2113.ccr42.dca01.atlas.cogentco.com (154.54.24.221) 998.858 ms be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 249.930 ms * 14 be2807.ccr42.jfk02.atlas.cogentco.com (154.54.40.109) 768.461 ms be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 136.772 ms be2807.ccr42.jfk02.atlas.cogentco.com (154.54.40.109) 288.225 ms 15 be2094.ccr21.bos01.atlas.cogentco.com (154.54.30.14) 271.736 ms 166.224 ms be2096.ccr22.bos01.atlas.cogentco.com (154.54.30.42) 565.015 ms 16 te0-4-1-7.agr22.bos01.atlas.cogentco.com (154.54.80.34) 1944.479 ms te0-4-1-6.agr22.bos01.atlas.cogentco.com (154.54.80.10) 149.803 ms te0-4-1-6.agr21.bos01.atlas.cogentco.com (154.54.47.230) 897.115 ms 17 te0-0-2-0.nr11.b000254-0.bos01.atlas.cogentco.com (154.24.9.82) 107.207 ms te0-0-2-1.nr11.b000254-0.bos01.atlas.cogentco.com (154.24.9.78) 295.881 ms 185.453 ms 18 38.122.127.18 (38.122.127.18) 115.652 ms 461.168 ms 615.526 ms 19 207.154.0.57 (207.154.0.57) 1871.023 ms 1987.832 ms 2165.248 ms 20 server1.ntcorp.com (207.154.13.58) 587.560 ms 263.328 ms 333.542 ms Traceroute in the reverse direction: 1 207.154.13.47 (207.154.13.47) 0.000 ms 0.000 ms 0.000 ms 2 * * * 3 h130.207.190.173.static.ip.windstream.net (173.190.207.130) 0.000 ms 0.000 ms 0.000 ms 4 xe1-2-0-0.cr01.cley01-oh.us.windstream.net (40.128.250.166) 12.000 ms 12.000 ms 12.000 ms 5 et11-0-0-0.cr01.chcg01-il.us.windstream.net (40.128.248.71) 20.000 ms 20.000 ms 20.000 ms 6 10gigabitethernet4-1.core1.chi1.he.NET (206.223.119.37) 72.001 ms 20.000 ms 16.000 ms 7 chgobbrj01pos010100.r2.ch.cox.net (68.105.30.193) 20.000 ms 20.000 ms 20.000 ms 8 chnddsrj01-ae1.0.rd.ph.cox.net (68.1.5.211) 72.001 ms 72.001 ms 72.001 ms 9 * * * 10 * * * 11 * * * <snip> 30 * * * <looks like a lot of the later hops don't respond to pings> Two things jump out at me: 1. The rather large number of hops from cox to ntcorp - with high delays from several nodes in both the level3 and cogent networks. 2. That there's a rather more direct path from the datacenter to cox, that shows up in the reverse direction. Some kind of routing or peering issue, perhaps? (And I also note the earlier string of messages regarding youtube streaming problems - that also seemed to involve cox and level3. Thanks for any insight (and better, for any fixes!). Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra

2 4

Small-mid scale vDPI
by Ramy Hashish 13 Feb '17

13 Feb '17

Good day community, Any experience based recommendations about cost effective vDPIs in small-mid scale? Thanks, Ramy

1 0

YouTube streaming failures
by Mel Beckman 13 Feb '17

13 Feb '17

We are getting many customer reports of YouTube streaming failures. The content directory and search work, but attempts to view videos results in "something went wrong, click to try again" error messages. We've reproduced the problem on AT&T, Level3, Frontier, Cox and Comast networks. We are also seeing it on cellular data connections, which tends to rule out geo-IP errors. Is anyone else seeing this? -mel beckman

5 5

Call for presentations - FIR 2017
by Fabián Mejía 11 Feb '17

11 Feb '17

*********************************************************************** CALL FOR PRESENTATIONS *********************************************************************** REGIONAL INTERCONNECTION FORUM 2017 May 22-26, 2017 – Foz do Iguazu, Brasil More information: http://interconexion.lacnic.net LACNIC (http://www.lacnic.net) is an international organization based in Montevideo, Uruguay, responsible for administrating IP address space, Reverse Resolution, Autonomous System Numbers and other resources for the region of Latin America and the Caribbean on behalf of the Internet community. The Regional Interconnection Forum (formerly known as NAPLA), is a discussion forum that includes an annual meeting held within the framework of LACNIC's main annual event. The LACNIC 27 event (http://www.lacnic.net/web/eventos/lacnic27) will be held in Foz do Iguazu (Brasil) on 22-26 May, 2017, so we are calling the Internet community to submit proposals for presentations that could be included on the 2017 Regional Interconnection Forum's program. The topics of interest for the event include, but are not limited to, the following: * Internet Exchange Points (IXPs): current status, future projects, new services, public policies, multimedia peering,. * Regional Connectivity: the role of governments, submarine and terrestrial cables, traffic measurements, current and future needs. * Content Delivery Networks (CDNs): strategies of deployment and presence within the region, peering policies, impact on local and regional traffic, * Cloud services: impact on local and regional traffic, availability, growth, future projects in the LAC region. * Other critical infrastructure: DNS root servers, ccTLDs and gTLDs. * Technical topics: best BGP routing practices, analysis of faults and attacks having major impacts on traffic. * Current issues: impact on local or regional traffic of high-interest events (e.g., availability / unavailability of services, natural disasters, sports events of high interest, etc). GUIDELINES FOR THE SUBMISSION OF PROPOSALS: Those interested in presenting a proposal should send an email to comite.fir@ lacnic.net containing the following information in the text of the message: * Presentation title. * General summary. * An attachment with a draft of the slides or an extended abstract of the article / work submitted. This text should not exceed one thousand (1000) words. * Estimated time of the presentation. * Authors' details (full name, email address and company/organization they represent) * Specify whether at least one of the authors can guarantee their attendance at the event, or whether this depends on the possibility of obtaining financial assistance from the event's organizers (see "Speaker Benefits"). In addition, the following considerations should be taken into account: * Proposals may be submitted in English, Portuguese or Spanish. * Proposals must be submitted in Portable Document Format (PDF). * Scanned documents will not be accepted. * Presentations may not be longer than 20 minutes. The time allocated may be different than requested. * The Evaluation Committee may, at its sole discretion, request additional information, which must be sent promptly. PROPOSAL EVALUATION: The Evaluation Committee created for this purpose shall evaluate proposals based on the following basic criteria: * Originality * Value of sharing the experience * Technical quality * Relevance * Possibility of generalized application * Presentation * Applicability * Importance of the development THE EVALUATION COMMITTEE IS MADE UP AS FOLLOWS: * Roque Gagliano (UY) * Milton Kashiwakura (BR) * Hernan Arcidiacono (AR) * Mauricio Oviedo (CR) * Gabriel Adonaylo (AR) * Christian O'Flaherty (AR) * Carlos Martínez (UY) * Fabián Mejía (EC) SPEAKER BENEFITS: The registration fee will be waived for those authors whose proposals are accepted and included in the program. However, speaker travel and accommodation expenses will not be covered. Those requiring financial assistance to attend the event may apply for such assistance when LACNIC opens the corresponding application period. Please note that acceptance of a proposal does NOT imply that the author(s) will be granted financial assistance, although the submission of a proposal may be considered a plus during the recipient selection process. For more information, please check out the Financial Assistance section on the event's website: (http://www.lacnic.net/web/eventos/lacnic27) or check with LACNIC staff at becas(a)lacnic.net IMPORTANT DATES: * Deadline for proposal reception: Sunday, 12 March 2017 * Notification of acceptance: Week of March 13, 2017 * Deadline for submitting the final version of the presentation: Friday, 12 May, 2017 Kind regards, Fabian Mejia Chair Regional Interconnection Forum

1 0

Dev. Mfg & ISP Filtering Requirements as set forth in Florida HB337/SB0870, and under similar bills in about 30 other states...
by Kraig Beahn 11 Feb '17

11 Feb '17

There's a bill being widely circulated and passing thru various chambers of at least 30 states right now, commonly being referred to as the HUMAN TRAFFICKING AND CHILD EXPLOITATION PREVENTION ACT, or in Florida's case, we're apparently calling this the "HB 337:Internet Access" bill. Jokes, moral considerations and politics aside - Does anyone have any further information on potentially related bills passing thru states beyond Florida, and has anyone seriously considered the infrastructure changes/impairments necessary to comply, in the unusual event that HB337 or any of the many other bills in various other states passes? Edited HB Brief: An act relating to Internet access; prohibiting covered businesses from manufacturing, distributing, or selling certain devices unless the device contains an active and operating filter that blocks Internet access to specified types of sexually oriented material, prostitution, assignation, lewdness, and human trafficking; providing for injunctive relief for violations; providing requirements for a consumer to have such filter deactivated; requiring a filter deactivation fee and providing for the collection and distribution thereof; prohibiting the distribution or sale of certain devices without filters to minors and adults; providing criminal penalties; providing for jurisdiction to prosecute violations; providing for continuing duties of covered businesses; requiring covered businesses to respond to reports of obscene material that has breached the filter; providing for civil penalties for violations; requiring covered businesses to unblock non obscene material; exempting certain websites from filtering; amending s. 16.56, F.S.; authorizing the Office of Statewide Prosecution to prosecute violations; providing an effective date. The Full Text can be found here: FL/HB 337 <http://www.flsenate.gov/Session/Bill/2017/0337/BillText/__/PDF> On the technical side, you'd probably find yourself chuckling through this reading exercise. However, our regulatory attorney was assured this bill for which is currently under consideration is no laughing matter and is being seriously considered in a multitude of state venues, while others have been dismissive. We've initiated several calls with aide's for Rep. Spanos, the Florida House sponsor, and from what we can tell, the bill is far from the chopping block. Considering the technical impacts not only to internet access device manufacturers, and the implied impacts on service providers like ourselves, i'm surprised it hasn't garnered more attention, nationally. >From a curiosity perspective: The source of this bill appears to be an individual by the name Mark "Chris" Sevier, the same individual whom has virtually sued most of Silicon Valley, and I'll leave it at that in hopes of being able to keep this thread on a technical/legislative tone. NANOG note: Our objective in starting this tread is not to question the intent, moral purpose or potential political agendas surrounding Florida House Bill 337 or bills of similar nature, only it's technical impact on device manufacturers, internet access providers and other alike legislatively covered businesses, assuming passage, as currently written. --

2 1

IoT security
by William Herrin 10 Feb '17

10 Feb '17

This afternoon's panel about IoT's lack of security got me thinking... On the issue of ISPs unable to act on insecure devices because they can't detect the devices until they're compromised and then only have the largest hammer (full account ban) to act... What about some kind of requirement or convention that upon boot and successful attachment to the network (and maybe once a month thereafter), any IoT device must _by default_ emit a UDP packet to an anycast address reserved for the purpose which identifies the device model and software build. The ISP can capture traffic to that anycast address, compare the data against a list of devices known to be defective and, if desired, respond with a fail message. If the IoT device receives the fail message, it must try to report the problem to its owner and remove its default route so that it can only communicate on the local lan. The user can override the fail and if desired configure the device not to emit the init messages at all. But by default the ISP is allowed to disable the device by responding to the init message. Would have to cryptographically sign the fail message and let the device query the signer's reputation or something like that to avoid the obvious security issue. Obvious privacy issues to consider. Anyway, throwing it out there as a potential discussion starting point. The presentation on bandwidth policers... Seems like we could use some form of ICMP message similar to destination unreachable that provides some kind of arbitrary string plus the initial part of the dropped packet. One of the potential strings would be an explicit notice to the sender that packets were dropped and the bandwidth available. Yes, we already have ECN, but ECN tells the receiver about congestion, not the sender. More to the point, ECN can only be flagged on packets that are passed, not the packets that are dropped, so the policer would have to be complicated enough to note on the next packet that the prior packet was dropped. Also, ECN only advises that you're close to the limit not any information about the policer's target limit. This thought is not fully baked. Throwing it out for conversation purposes. Regards, Bill Herrin -- William Herrin ................ herrin(a)dirtside.com bill(a)herrin.us Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/>

16 33

Gmail or GAFYD SREs on the list?
by Brad Knowles 10 Feb '17

10 Feb '17

Folks, Do we have any SREs from the Gmail or Google Apps For Your Domain teams on the list? I’m helping to support some domains related to the Network Time Foundation and NTP.org, and we’re having some problems with IPv6 connectivity to them. Thanks! -- Brad Knowles <brad(a)shub-internet.org>

1 0

Someone's scraping NANOG for phishing purposes again
by Alexander Harrowell 10 Feb '17

10 Feb '17

I'm getting suspicious e-mail pretending to come from leading NANOGers. Not the first time this has happened, but you may want to be warned. Yours, Alex Harrowell

7 8

Weekly Routing Table Report
by cscora＠apnic.net 10 Feb '17

10 Feb '17

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, AusNOG, SANOG, PacNOG, MENOG, SAFNOG, SdNOG, BJNOG, CaribNOG 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 11 Feb, 2017 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 635010 Prefixes after maximum aggregation (per Origin AS): 247431 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 305846 Total ASes present in the Internet Routing Table: 56204 Prefixes per ASN: 11.30 Origin-only ASes present in the Internet Routing Table: 48647 Origin ASes announcing only one prefix: 21683 Transit ASes present in the Internet Routing Table: 7557 Transit-only ASes present in the Internet Routing Table: 208 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 41 Max AS path prepend of ASN ( 55644) 36 Prefixes from unregistered ASNs in the Routing Table: 80 Numnber of instances of unregistered ASNs: 81 Number of 32-bit ASNs allocated by the RIRs: 17256 Number of 32-bit ASNs visible in the Routing Table: 13413 Prefixes from 32-bit ASNs in the Routing Table: 53971 Number of bogon 32-bit ASNs visible in the Routing Table: 50 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 429 Number of addresses announced to Internet: 2832797668 Equivalent to 168 /8s, 217 /16s and 15 /24s Percentage of available address space announced: 76.5 Percentage of allocated address space announced: 76.5 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.4 Total number of prefixes smaller than registry allocations: 211930 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 173285 Total APNIC prefixes after maximum aggregation: 49607 APNIC Deaggregation factor: 3.49 Prefixes being announced from the APNIC address blocks: 172688 Unique aggregates announced from the APNIC address blocks: 71398 APNIC Region origin ASes present in the Internet Routing Table: 7845 APNIC Prefixes per ASN: 22.01 APNIC Region origin ASes announcing only one prefix: 2190 APNIC Region transit ASes present in the Internet Routing Table: 1119 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 41 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2672 Number of APNIC addresses announced to Internet: 760441732 Equivalent to 45 /8s, 83 /16s and 107 /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-137529 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: 193476 Total ARIN prefixes after maximum aggregation: 92928 ARIN Deaggregation factor: 2.08 Prefixes being announced from the ARIN address blocks: 195792 Unique aggregates announced from the ARIN address blocks: 89820 ARIN Region origin ASes present in the Internet Routing Table: 17789 ARIN Prefixes per ASN: 11.01 ARIN Region origin ASes announcing only one prefix: 6642 ARIN Region transit ASes present in the Internet Routing Table: 1766 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: 1756 Number of ARIN addresses announced to Internet: 1104034720 Equivalent to 65 /8s, 206 /16s and 59 /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-397212 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: 169226 Total RIPE prefixes after maximum aggregation: 83704 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 164564 Unique aggregates announced from the RIPE address blocks: 99725 RIPE Region origin ASes present in the Internet Routing Table: 23672 RIPE Prefixes per ASN: 6.95 RIPE Region origin ASes announcing only one prefix: 10968 RIPE Region transit ASes present in the Internet Routing Table: 3356 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 28 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5534 Number of RIPE addresses announced to Internet: 709553024 Equivalent to 42 /8s, 74 /16s and 235 /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-207259 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: 82544 Total LACNIC prefixes after maximum aggregation: 17448 LACNIC Deaggregation factor: 4.73 Prefixes being announced from the LACNIC address blocks: 83648 Unique aggregates announced from the LACNIC address blocks: 37823 LACNIC Region origin ASes present in the Internet Routing Table: 5645 LACNIC Prefixes per ASN: 14.82 LACNIC Region origin ASes announcing only one prefix: 1557 LACNIC Region transit ASes present in the Internet Routing Table: 1039 Average LACNIC Region AS path length visible: 5.3 Max LACNIC Region AS path length visible: 36 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 3161 Number of LACNIC addresses announced to Internet: 170804288 Equivalent to 10 /8s, 46 /16s and 68 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-266652 + 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: 16366 Total AfriNIC prefixes after maximum aggregation: 3683 AfriNIC Deaggregation factor: 4.44 Prefixes being announced from the AfriNIC address blocks: 17889 Unique aggregates announced from the AfriNIC address blocks: 6717 AfriNIC Region origin ASes present in the Internet Routing Table: 1017 AfriNIC Prefixes per ASN: 17.59 AfriNIC Region origin ASes announcing only one prefix: 326 AfriNIC Region transit ASes present in the Internet Routing Table: 198 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 18 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 290 Number of AfriNIC addresses announced to Internet: 87502592 Equivalent to 5 /8s, 55 /16s and 47 /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 5531 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3724 391 256 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2984 905 71 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2729 11133 744 KIXS-AS-KR Korea Telecom, KR 9829 2718 1501 542 BSNL-NIB National Internet Backbone, IN 9808 2283 8698 33 CMNET-GD Guangdong Mobile Communication 4755 2058 421 220 TATACOMM-AS TATA Communications formerl 45899 1861 1299 100 VNPT-AS-VN VNPT Corp, VN 4808 1636 1784 445 CHINA169-BJ China Unicom Beijing Provin 24560 1564 571 250 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 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 22773 3629 2968 151 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6327 3260 1333 83 SHAW - Shaw Communications Inc., CA 18566 2191 405 109 MEGAPATH5-US - MegaPath Corporation, US 6389 2063 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 20115 1970 2034 406 CHARTER-NET-HKY-NC - Charter Communicat 209 1725 5067 640 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1688 317 459 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6983 1680 848 227 ITCDELTA - Earthlink, Inc., US 16509 1642 3064 537 AMAZON-02 - Amazon.com, Inc., US 701 1594 10597 657 UUNET - MCI Communications Services, In 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 39891 3334 171 18 ALJAWWALSTC-AS , SA 20940 3013 1129 2135 AKAMAI-ASN1 , US 9121 2138 1691 18 TTNET , TR 34984 1994 328 380 TELLCOM-AS , TR 13188 1615 99 62 TRIOLAN , UA 8551 1607 377 46 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12479 1468 1033 50 UNI2-AS , ES 6849 1318 355 22 UKRTELNET , UA 9198 1300 352 24 KAZTELECOM-AS , KZ 8402 1151 544 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 10620 3541 545 158 Telmex Colombia S.A., CO 26615 3027 2330 44 Tim Celular S.A., BR 8151 2488 3390 549 Uninet S.A. de C.V., MX 11830 1804 368 66 Instituto Costarricense de Electricidad 6503 1570 437 54 Axtel, S.A.B. de C.V., MX 7303 1430 878 255 Telecom Argentina S.A., AR 6147 1353 377 27 Telefonica del Peru S.A.A., PE 28573 1059 2273 182 CLARO S.A., BR 3816 1001 479 185 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11664 984 280 35 Techtel LMDS Comunicaciones Interactiva 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 1298 398 41 LINKdotNET-AS, EG 36903 719 361 123 MT-MPLS, MA 37611 690 67 6 Afrihost, ZA 36992 587 1373 25 ETISALAT-MISR, EG 24835 490 658 16 RAYA-AS, EG 8452 461 1474 16 TE-AS TE-AS, EG 37492 392 316 74 ORANGE-TN, TN 29571 367 36 10 CITelecom-AS, CI 15399 327 35 6 WANANCHI-KE, KE 2018 273 327 74 TENET-1, ZA 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 4538 5531 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3724 391 256 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3629 2968 151 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3541 545 158 Telmex Colombia S.A., CO 39891 3334 171 18 ALJAWWALSTC-AS , SA 6327 3260 1333 83 SHAW - Shaw Communications Inc., CA 26615 3027 2330 44 Tim Celular S.A., BR 20940 3013 1129 2135 AKAMAI-ASN1 , US 17974 2984 905 71 TELKOMNET-AS2-AP PT Telekomunikasi Indo 4766 2729 11133 744 KIXS-AS-KR Korea Telecom, KR Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 3629 3478 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3724 3468 TPG-INTERNET-AP TPG Telecom Limited, AU 10620 3541 3383 Telmex Colombia S.A., CO 39891 3334 3316 ALJAWWALSTC-AS , SA 6327 3260 3177 SHAW - Shaw Communications Inc., CA 26615 3027 2983 Tim Celular S.A., BR 17974 2984 2913 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 9808 2283 2250 CMNET-GD Guangdong Mobile Communication Co.Ltd. 9829 2718 2176 BSNL-NIB National Internet Backbone, IN 9121 2138 2120 TTNET , TR Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65001 PRIVATE 5.143.176.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65602 UNALLOCATED 8.225.192.0/24 30372 SUNESYS2 - Sunesys, LLC, US 65001 PRIVATE 31.172.192.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.200.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.208.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.216.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65000 PRIVATE 31.219.177.0/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65000 PRIVATE 31.219.177.128/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65555 UNALLOCATED 37.142.172.0/24 21450 MIRS-AS , IL Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 41.73.16.0/24 37004 Suburban-Broadband-AS, NG 41.73.17.0/24 37004 Suburban-Broadband-AS, NG 41.73.18.0/24 37004 Suburban-Broadband-AS, NG 41.73.19.0/24 37004 Suburban-Broadband-AS, NG 41.73.20.0/24 37004 Suburban-Broadband-AS, NG 41.73.21.0/24 37004 Suburban-Broadband-AS, NG 41.73.22.0/24 37004 Suburban-Broadband-AS, NG 41.73.23.0/24 37004 Suburban-Broadband-AS, NG 41.76.232.0/21 203496 AB-TELECOM , RU 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:16 /9:13 /10:36 /11:103 /12:276 /13:535 /14:1047 /15:1801 /16:13175 /17:7751 /18:12998 /19:25124 /20:38119 /21:40837 /22:74093 /23:62687 /24:355030 /25:561 /26:415 /27:294 /28:35 /29:19 /30:18 /31:1 /32:26 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3056 3260 SHAW - Shaw Communications Inc., CA 39891 2896 3334 ALJAWWALSTC-AS , SA 22773 2825 3629 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 26615 2543 3027 Tim Celular S.A., BR 18566 2084 2191 MEGAPATH5-US - MegaPath Corporation, US 9121 1503 2138 TTNET , TR 30036 1499 1688 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1452 3541 Telmex Colombia S.A., CO 6389 1372 2063 BELLSOUTH-NET-BLK - BellSouth.net Inc., US 13188 1359 1615 TRIOLAN , UA Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1596 2:832 4:25 5:2443 6:34 8:1047 12:1810 13:74 14:1777 15:22 16:2 17:100 18:128 19:1 20:53 23:2012 24:1847 25:2 27:2385 31:1858 32:89 33:2 34:1 35:3 36:357 37:2526 38:1308 39:43 40:101 41:2846 42:452 43:1929 44:59 45:2382 46:2548 47:110 49:1218 50:945 51:18 52:709 54:357 55:7 56:4 57:41 58:1616 59:989 60:386 61:1898 62:1505 63:1928 64:4558 65:2185 66:4451 67:2222 68:1168 69:3324 70:1302 71:570 72:2050 74:2609 75:405 76:411 77:1436 78:1583 79:1280 80:1342 81:1401 82:982 83:722 84:869 85:1691 86:482 87:1132 88:781 89:2054 90:201 91:6125 92:985 93:2378 94:2356 95:2793 96:570 97:357 98:936 99:91 100:152 101:1261 103:13569 104:2706 105:147 106:482 107:1530 108:794 109:2575 110:1287 111:1662 112:1149 113:1234 114:1028 115:1733 116:1745 117:1649 118:2056 119:1564 120:952 121:1099 122:2341 123:2016 124:1527 125:1813 128:745 129:616 130:412 131:1391 132:520 133:193 134:529 135:209 136:505 137:430 138:1841 139:499 140:367 141:518 142:731 143:908 144:764 145:167 146:1021 147:658 148:1361 149:569 150:686 151:938 152:722 153:316 154:750 155:963 156:548 157:589 158:443 159:1393 160:566 161:734 162:2473 163:528 164:782 165:1153 166:370 167:1260 168:2519 169:738 170:2777 171:275 172:934 173:1827 174:805 175:720 176:1774 177:4234 178:2477 179:1644 180:2096 181:2032 182:2210 183:1041 184:830 185:8713 186:3208 187:2684 188:2367 189:1786 190:8138 191:1945 192:9288 193:5777 194:4624 195:3845 196:1957 197:1231 198:5572 199:5835 200:7387 201:4132 202:10117 203:9879 204:4454 205:2772 206:2985 207:3150 208:3999 209:3882 210:3914 211:2096 212:2789 213:2456 214:861 215:64 216:5814 217:1988 218:834 219:607 220:1685 221:901 222:723 223:1172 End of report

1 0

Telia network quality
by Don 10 Feb '17

10 Feb '17

I heard Telia's quality had been on the decline lately as they were signing on lots of high-capacity new customers, and Cloudflare had some complaint about them a few months prior too. Does anybody have any insight into whether this is still the case? I was trying to evaluate whether Telia would be a good carrier to switch over to as a primary provider, as their pricing does look pretty attractive. B/R Don

11 11