Talk:Cloudflare: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
Line 267: Line 267:
Cloudflare suffered a major outage on July 2, 2019,<ref>{{Cite web|last=Cheng|first=Michelle|date=July 15, 2019|title=Cloudflare shows how transparent tech companies should be|url=https://qz.com/work/1666535/cloudflare-turned-outage-into-teaching-point-about-transparency/|access-date=July 17, 2020|website=[[Quartz (publication)|Quartz]]}}</ref> which rendered more than 12 million websites (80% of all Cloudflare's customers) unreachable for 27 minutes.<ref name="auto">{{cite news|last=Graham-Cumming|first=John|date=July 12, 2019|title=Details of the Cloudflare outage on July 2, 2019|work=The Cloudflare Blog|url=https://blog.cloudflare.com/details-of-the-cloudflare-outage-on-july-2-2019/|access-date=July 12, 2019}}</ref> A similar outage occurred on July 17, 2020, with similar effect and impacting approximately the same number of sites.<ref>{{Cite web|last=Dassanayake|first=Dion|date=July 17, 2020|title=Discord DOWN: Server status latest, connection and chat problems confirmed|url=https://www.express.co.uk/entertainment/gaming/1311090/Discord-down-server-status-latest-connection-and-chat-problems|access-date=July 17, 2020|website=[[Daily Express]]}}</ref><ref>{{Cite web|last=Carpenter|first=Nicole|date=July 17, 2020|title=Discord, Riot Games down with reported Cloudflare outage|url=https://www.polygon.com/2020/7/17/21329005/cloudflare-outrage-discord-riot-games-july-2020|access-date=July 17, 2020|website=[[Polygon (website)|Polygon]]}}</ref> Other notable outages occurred on June 24, 2019 (two hours and twenty-seven minutes),<ref>{{cite news |last1=Perez |first1=Sarah |title=Cloudflare issues affecting numerous sites on Monday |url=https://techcrunch.com/2019/06/24/cloudflare-outage-affecting-numerous-sites-on-monday-am/ |access-date=16 June 2021 |publisher=TechCrunch |date=2019-06-24 |quote=Cloudflare is having network problems this morning — and taking down a lot of its customers’ sites and apps in the process. Affected companies include podcast app Overcast, chat service Discord, managed hosting provider WP Engine, eCommerce hosting provider Sonassi, public web front-end CDN service CDNJS, and many others — including the sites that rely on the web hosting or who partner with Cloudflare for their CDN service.}}</ref> April 1, 2020 (five hours and five minutes),<ref>{{cite web |last1=Medina |first1=Angelique |title=Why Rostelecom’s Route Hijack Highlights the Need for BGP Security |url=https://www.thousandeyes.com/blog/rostelecom-route-hijack-highlights-bgp-security |website=ThousandEyes |quote=On April 1, 2020, at 7:30 PM UTC, JSC Rostelecom announced a more specific /21 route to Cloudflare’s services. By 12:35 PM, all illegitimate routes were withdrawn, and traffic was flowing normally to affected services.}}</ref> August 30, 2020 (four hours and fifty-five minutes),<ref>{{cite news |last1=Goodwin |first1=Jazmin |title=Major internet outage: Dozens of websites and apps were down |url=https://www.cnn.com/2020/08/30/tech/internet-outage-cloudflare/index.html |access-date=16 June 2021 |publisher=CNN Business |date=2020-08-31 |quote=Cloudflare CTO Graham-Cumming claimed that CenturyLink was responsible for the outage, which took Cloudflare and its customers down with them. The outage followed a shorter one on Saturday.}}</ref> May 3, 2021 (two hours)<ref>{{cite web |last1=Medina |first1=Angelique |title=Even Magic Can't Stop Internet Outages |url=https://www.thousandeyes.com/blog/internet-report-episode-37 |website=ThousandEyes |access-date=16 June 2021 |quote=Today, we focused on an interesting outage that impacted Cloudflare. On May 3rd at approximately 22:00 UTC, ThousandEyes vantage points connecting to sites using Magic Transit began to detect significant packet loss at Cloudflare’s network edge—with the loss continuing at varying levels, for approximately 2 hours.}}</ref> and June 11, 2021 (one hour and five minutes).<ref>{{cite news |last1=Claburn |first1=Thomas |title=Cloudflare network outage disrupts Discord, Shopify |url=https://www.theregister.com/2021/06/11/cloudflare_outage_captcha/ |access-date=16 June 2021 |publisher=The Register |date=2021-06-11 |quote='Cloudflare is aware of an issue which potentially impacts multiple customers,' the company said. Chat service Discord, reported 'connection failures in US East due to issues upstream of our service.' Shopify likewise reported service issues around 1607 UTC and said the problems were resolved by 1712 UTC.}}</ref>
Cloudflare suffered a major outage on July 2, 2019,<ref>{{Cite web|last=Cheng|first=Michelle|date=July 15, 2019|title=Cloudflare shows how transparent tech companies should be|url=https://qz.com/work/1666535/cloudflare-turned-outage-into-teaching-point-about-transparency/|access-date=July 17, 2020|website=[[Quartz (publication)|Quartz]]}}</ref> which rendered more than 12 million websites (80% of all Cloudflare's customers) unreachable for 27 minutes.<ref name="auto">{{cite news|last=Graham-Cumming|first=John|date=July 12, 2019|title=Details of the Cloudflare outage on July 2, 2019|work=The Cloudflare Blog|url=https://blog.cloudflare.com/details-of-the-cloudflare-outage-on-july-2-2019/|access-date=July 12, 2019}}</ref> A similar outage occurred on July 17, 2020, with similar effect and impacting approximately the same number of sites.<ref>{{Cite web|last=Dassanayake|first=Dion|date=July 17, 2020|title=Discord DOWN: Server status latest, connection and chat problems confirmed|url=https://www.express.co.uk/entertainment/gaming/1311090/Discord-down-server-status-latest-connection-and-chat-problems|access-date=July 17, 2020|website=[[Daily Express]]}}</ref><ref>{{Cite web|last=Carpenter|first=Nicole|date=July 17, 2020|title=Discord, Riot Games down with reported Cloudflare outage|url=https://www.polygon.com/2020/7/17/21329005/cloudflare-outrage-discord-riot-games-july-2020|access-date=July 17, 2020|website=[[Polygon (website)|Polygon]]}}</ref> Other notable outages occurred on June 24, 2019 (two hours and twenty-seven minutes),<ref>{{cite news |last1=Perez |first1=Sarah |title=Cloudflare issues affecting numerous sites on Monday |url=https://techcrunch.com/2019/06/24/cloudflare-outage-affecting-numerous-sites-on-monday-am/ |access-date=16 June 2021 |publisher=TechCrunch |date=2019-06-24 |quote=Cloudflare is having network problems this morning — and taking down a lot of its customers’ sites and apps in the process. Affected companies include podcast app Overcast, chat service Discord, managed hosting provider WP Engine, eCommerce hosting provider Sonassi, public web front-end CDN service CDNJS, and many others — including the sites that rely on the web hosting or who partner with Cloudflare for their CDN service.}}</ref> April 1, 2020 (five hours and five minutes),<ref>{{cite web |last1=Medina |first1=Angelique |title=Why Rostelecom’s Route Hijack Highlights the Need for BGP Security |url=https://www.thousandeyes.com/blog/rostelecom-route-hijack-highlights-bgp-security |website=ThousandEyes |quote=On April 1, 2020, at 7:30 PM UTC, JSC Rostelecom announced a more specific /21 route to Cloudflare’s services. By 12:35 PM, all illegitimate routes were withdrawn, and traffic was flowing normally to affected services.}}</ref> August 30, 2020 (four hours and fifty-five minutes),<ref>{{cite news |last1=Goodwin |first1=Jazmin |title=Major internet outage: Dozens of websites and apps were down |url=https://www.cnn.com/2020/08/30/tech/internet-outage-cloudflare/index.html |access-date=16 June 2021 |publisher=CNN Business |date=2020-08-31 |quote=Cloudflare CTO Graham-Cumming claimed that CenturyLink was responsible for the outage, which took Cloudflare and its customers down with them. The outage followed a shorter one on Saturday.}}</ref> May 3, 2021 (two hours)<ref>{{cite web |last1=Medina |first1=Angelique |title=Even Magic Can't Stop Internet Outages |url=https://www.thousandeyes.com/blog/internet-report-episode-37 |website=ThousandEyes |access-date=16 June 2021 |quote=Today, we focused on an interesting outage that impacted Cloudflare. On May 3rd at approximately 22:00 UTC, ThousandEyes vantage points connecting to sites using Magic Transit began to detect significant packet loss at Cloudflare’s network edge—with the loss continuing at varying levels, for approximately 2 hours.}}</ref> and June 11, 2021 (one hour and five minutes).<ref>{{cite news |last1=Claburn |first1=Thomas |title=Cloudflare network outage disrupts Discord, Shopify |url=https://www.theregister.com/2021/06/11/cloudflare_outage_captcha/ |access-date=16 June 2021 |publisher=The Register |date=2021-06-11 |quote='Cloudflare is aware of an issue which potentially impacts multiple customers,' the company said. Chat service Discord, reported 'connection failures in US East due to issues upstream of our service.' Shopify likewise reported service issues around 1607 UTC and said the problems were resolved by 1712 UTC.}}</ref>
:I agree that this paragraph on outages is, at a minimum, misplaced and likely unnecessary. There is no coverage from the mainstream press on these routine issues. Outages can be notable; The 8 June Fastly outage is an example. Based on the citations included, I see nothing that rises to that level here. ~[[User:Kvng|Kvng]] ([[User talk:Kvng|talk]]) 14:47, 24 June 2021 (UTC)
'''Second Request'''
'''Second Request'''

Revision as of 14:48, 24 June 2021

WikiProject iconGuild of Copy Editors
WikiProject iconThis article was copy edited by a member of the Guild of Copy Editors.

Request Edits February 2021

{{request edit}} has been deprecated. Please change this template call to one of the following:

  • For edit requests relating to a conflict of interest, please use {{edit COI}}.
  • If you are partially-blocked from editing the page, please use {{edit partially-blocked}}.
  • If the page is protected, use one of the following:
    • {{SPER}} for semi-protected pages
    • {{EPER}} for extended-confirmed protected pages
    • {{TPER}} for template-protected pages
    • {{FPER}} for fully-protected pages
    • {{IAER}} for interface admin protected pages

If you simply need to ask for help in making an edit, please change the template to {{help me}}.

Hello. I’d like to propose the following changes to help improve the neutrality and sourcing in this article. I’m an employee of Cloudflare and I have a conflict of interest so it would be great if an independent editor could review them. Thanks for your consideration.

  • Thank you for following good WP:COI practices. I don't have time today to make more than one change I did, but I will take a look another day. (And hopefully some other editors look in the meantime, too.) - Dyork (talk) 02:02, 13 February 2021 (UTC)[reply]

1.In the lead, please replace the first three sentences: Cloudflare, Inc. is an American web infrastructure and website security company, providing content delivery network services, DDoS mitigation, Internet security, and distributed domain name server services. Cloudflare's services sit between a website's visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites. Cloudflare's headquarters are in San Francisco.

WITH:

Cloudflare, Inc. is an American web infrastructure and website security company that provides content delivery network services, DDoS mitigation, Internet security, and distributed domain name server services.[1] Cloudflare's services sit between a website's visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.[2][3] Cloudflare's headquarters are in San Francisco.[1]

  • Explanation: The language is virtually identical (corrects one grammar mistake), but updates the lead to include missing reliable sources. There are currently no sources in the lead.

2. In the History section, please replace the first sentence: Cloudflare was created in 2009 by Matthew Prince, Lee Holloway, and Michelle Zatlyn.[4]

WITH:

Cloudflare was created in 2009 by Matthew Prince, Lee Holloway, and Michelle Zatlyn, all three of whom previously worked on Project Honey Pot, an open-source project that monitored internet fraud and abuse.[5] Cloudflare was launched at the TechCrunch Disrupt conference in September 2010.[6]

  • Explanation: Replaces primary sources with secondary sources, and adds background details about co-founders’ history and company launch date, commensurate with articles about similar, large technology companies in the space such Amazon Web Services (B-Class article). Also in line with Wikipedia Good Article best practices for company articles such as Comverse Technology.

3. In the second paragraph of the History section, after this sentence: “Cloudflare has also reportedly absorbed attacks that have peaked over 400Gbit/s from an NTP Reflection attack.[7]

PLEASE ADD:

In June 2020, Cloudflare mitigated a DDoS attack that peaked at 754 million packets per second.[8] As of 2020, Cloudflare provides DNS services to over 100,000 customers, covering more than 25 million internet properties.[9][10]

  • Explanation: Updates the article with one of the largest DDoS attacks ever handled by the company, and a reliable source to support the sentence. Adds information regarding scope of Cloudflare’s service base with supporting reliable news sources, commensurate with articles about similar, large technology companies such as Amazon Web Services#Customer base (B-class). Also in line with Wikipedia Good Article best practices for company articles that discuss the size/scope of the business such as Pixar and Yelp.

4. In the History section, please replace the first sentence in the third paragraph: “In 2014, Cloudflare introduced an effort called Project Galileo in response to cyberattacks against vulnerable online targets, such as artists, activists, journalists, and human rights groups. Project Galileo provides such groups with free services to protect their websites. In 2019, Cloudflare announced that 600 users and organizations were participating in the project.[11]

WITH:

In 2014, Cloudflare launched Project Galileo, an initiative providing free services to protect artists, activists, journalists, and human rights groups from cyber attacks.[11] More than 1,000 users and organizations were participating in Project Galileo as of 2020.[12]

  • Explanation: Rewrites paragraph for clarity and grammar, and updates participant number for Project Galileo. Adds reliable sourcing to each statement.

5. In the History section, after the third paragraph that starts “In 2014, Cloudflare introduced an effort called Project Galileo…”

PLEASE ADD A NEW FOURTH PARAGRAPH:

Cloudflare created the Athenian Project in 2017 to ensure free protection of online election infrastructures to local and state governments, as well as domestic and foreign political campaigns.[13][14][15]

  • Explanation: Updates History section to include a notable event in the company’s history supported by prominent reliable sources such as CNBC and Fast Company.
  •  Done: Added but the location had to be a bit higher up to keep chronological order. Boredathome101 (talk) 04:11, 12 May 2021 (UTC)[reply]

6. In the History section, please replace the last paragraph: In 2020, co-founder and COO Michelle Zatlyn was named president,[16] making her one of few women serving as President of a publicly traded technology company in the United States.[16]

WITH:

In 2020, co-founder and COO Michelle Zatlyn was named president of Cloudflare, making her one of few women leading a publicly traded technology company in the United States.[16]

  • Explanation: Slightly rewrites the sentence for clarity, and eliminates repetition of the Fast Company source.
  •  Done - Adjusted the sentence to remove the redundant source. Did not add "of Cloudflare" as that seems redundant since this is the Cloudflare article. - Dyork (talk) 02:02, 13 February 2021 (UTC)[reply]

7. In the History section, as the new last paragraph, please add:

In January 2021, the company established the Project Fair Shot initiative, a free tool that enables global health organizations to maintain a digital queue for COVID-19 vaccinations.[17]
  • Explanation:: Updates article with the most recent company news, with supporting reliable source.

8. Move the Acquisitions section to be after the History section:

  • Eager Platform Co. (December 2016) [18]
  • Neumob (November 2017)[19]
  • S2 Systems (January 2020)[20][21]
  • Linc (December 2020)[22]

AND REPLACE THE CONTENT WITH:

Cloudflare acquired StopTheHacker, an anti-malware firm, in 2014.[23][24] In December 2016, Cloudflare acquired Eager Platform, a company that created a platform for drag-and-drop installation of apps.[25] The company acquired mobile VPN startup Neumob in 2017.[26][19] In 2020, Cloudflare acquired S2, a company that develops browser isolation technology, and Linc, an automation platform.[23][22]

  •  Done: but partially. Moved it up, used teh better sources, but left in bullet point list...much better that way. It would be be issue if the list of acquisitions grows, so it's much easily readable this way. Boredathome101 (talk) 04:22, 12 May 2021 (UTC)[reply]


Thank you for your consideration.Ryanknight24 (talk) 18:37, 12 February 2021 (UTC)[reply]


@Itsquietuptown: @Dyork: Thank you for beginning the review of my Feb 2021 Requested Edits for Cloudflare at Talk:Cloudflare. As there are still a number of unreviewed requests, I’d like to see if you might have time to take another look.

Thank you! Ryanknight24 (talk) 01:20, 4 March 2021 (UTC)[reply]

The following Request Edits have not yet been reviewed #2, #3, #4, #5, #7, #8, as of April 5, 2021. Thank you. Ryanknight24 (talk) 02:08, 7 April 2021 (UTC)[reply]


References

  1. ^ a b Clifford, Tyler (6 October 2020). "Cloudflare CEO: Dozens of U.S. states are using Athenian Project for election security". CNBC. Retrieved 25 January 2021.
  2. ^ Perlroth, Nicole (17 February 2012). "Search Bits SEARCH Preparing for DDoS Attacks or Just Groundhog Day". The New York Times. Retrieved 25 January 2021.
  3. ^ Durant, Richard (19 May 2020). "Cloudflare: Thinking Big". Seeking Alpha. Retrieved 25 January 2021.
  4. ^ "Our Story". Cloudflare. Retrieved August 22, 2019.
  5. ^ Loizos, Connie (15 August 2019). "Cloudflare, in its IPO filing, thanks a third co-founder: Lee Holloway". TechCrunch. Retrieved 25 January 2021.
  6. ^ Lardinois, Frederic (27 November 2019). "Cloudflare CEO Matthew Prince is Coming to Disrupt Berlin". TechCrunch. Retrieved 28 January 2021.
  7. ^ Gallagher, Sean (February 11, 2014). "Biggest DDoS ever aimed at Cloudflare's content delivery network". Ars Technica. Retrieved May 17, 2016.
  8. ^ Newman, Lily (15 July 2020). "'DDoS-For-Hire' Is Fueling a New Wave of Attacks". Wired. Retrieved 28 January 2021.
  9. ^ Witkowski, Wallace (5 November 2020). "Cloudflare stock rallies on better-than-expected results, outlook". MarketWatch. Retrieved 28 January 2021.
  10. ^ Lagorio-Chafkin, Christine (9 November 2020). "Why the CEO of a $350 Million Internet Security Company Practices Radical Transparency". Inc. Retrieved 28 January 2021.
  11. ^ a b Newman, Lily Hay (June 12, 2019). "Cloudflare's Five-Year Project to Protect Nonprofits Online". Wired. ISSN 1059-1028. Retrieved August 5, 2019.
  12. ^ Melendez, Steven (11 June 2020). "Amid pandemic and protests, Cloudflare is defending vulnerable websites". Fast Company. Retrieved 28 January 2021.
  13. ^ Clifford, Tyler (6 October 2020). "Cloudflare CEO: Dozens of U.S. states are using Athenian Project for election security". CNBC. Retrieved 28 January 2021.
  14. ^ Melendez, Steven (11 June 2020). "Amid pandemic and protests, Cloudflare is defending vulnerable websites". Fast Company. Retrieved 3 February 2021.
  15. ^ Hatmaker, Taylor (19 July 2018). "Cloudflare Recruits State and Local Governments for Free Election Site Security Programs". TechCrunch. Retrieved 28 January 2021.
  16. ^ a b c Mehta, Stephanie (2020-12-17). "Exclusive: Cloudflare promotes Michelle Zatlyn to president, a gain for women in tech". Fast Company. Retrieved 2020-12-20.
  17. ^ Etherington, Darrell (22 January 2021). "Cloudflare introduces free digital waiting rooms for any organizations distributing COVID-19 vaccines". TechCrunch. Retrieved 12 February 2021.
  18. ^ "Cloudflare Acquires Eager to Build Next-Generation App Platform For Its Massive Global Network". GlobeNewswire News Room. December 13, 2016. Retrieved September 18, 2020.
  19. ^ a b Ron Miller (November 14, 2017). "Neumob acquisition gives Cloudflare missing mobile component – TechCrunch". TechCrunch. Retrieved September 18, 2020.
  20. ^ Ron Miller (January 7, 2020). "Cloudflare acquires stealthy startup S2 Systems, announces Cloudflare for Teams – TechCrunch". TechCrunch. Retrieved September 17, 2020.
  21. ^ "Cloudflare Acquires S2 Systems Corporation for Next-Gen Browser Isolation". businesswire.com. January 7, 2020. Retrieved September 17, 2020.
  22. ^ a b Kyle Wiggers (December 22, 2020). "Cloudflare acquires Linc to automate web app deployment". VentureBeat. Retrieved December 22, 2020.
  23. ^ a b Kawamoto, Dawn (7 January 2020). "Fresh off IPO, this high-profile Bay Area cloud company just snapped up a browser isolation company". San Francisco Business Times. Retrieved 4 February 2021.
  24. ^ Lardonois, Frederic (24 February 2014). "CloudFlare Acquires Anit-Malware Firm StopTheHacker". TechCrunch. Retrieved 4 February 2021.
  25. ^ Yeung, Ken (13 December 2016). "Cloudflare acquires app platform Eager, will sunset service in Q1 2017". VentureBeat. Retrieved 4 February 2021.
  26. ^ Staff (14 November 2017). "Cloudflare Acquires App-Speed Startup Neumob". The Wall Street Journal. Retrieved 4 February 2021.

Request Edits May 2021

{{request edit}} has been deprecated. Please change this template call to one of the following:

  • For edit requests relating to a conflict of interest, please use {{edit COI}}.
  • If you are partially-blocked from editing the page, please use {{edit partially-blocked}}.
  • If the page is protected, use one of the following:
    • {{SPER}} for semi-protected pages
    • {{EPER}} for extended-confirmed protected pages
    • {{TPER}} for template-protected pages
    • {{FPER}} for fully-protected pages
    • {{IAER}} for interface admin protected pages

If you simply need to ask for help in making an edit, please change the template to {{help me}}.

Hello. I’d like to propose the following changes to help improve the neutrality and sourcing in this article. I’m an employee of Cloudflare and I have a conflict of interest so it would be great if an independent editor could review them, as explained on the Contact Us page for WIkipedia. Thanks for your consideration.

1. At the bottom of the “Products” section, after the “Pages” subsection.

PLEASE ADD A NEW SUB-SECTION.


VPNs The company offers a VPN called “WARP” that it says is for non-technical users. But unlike a standard VPN, the user does not get to choose their endpoint region. An ISP can’t monitor traffic that goes through the VPN. The WARP VPN cannot be used to access geo-restricted content.[1][2]

Explanation: This product has been covered in mainstream media outlets because it’s a popular consumer product.

  • COMMENT Adding a product might be too promotional, unless it has massive news coverage. If you can share maybe 5 more news sources about it, then I may review and reconsider. I will also let others to chime in. Boredathome101 (talk)

2. In the Products section, subsection DDoS, please delete the second paragraph:

On September 6, 2019, Wikipedia became the victim of a DDoS attack. European users were unable to access Wikipedia for several hours.[3] The attack was mitigated after Wikimedia network engineers used Cloudflare's network and DDoS protection services to re-route and filter internet traffic.[4] The specific Cloudflare product used was Magic Transit.[5]

AND MOVE TO THE SECOND TO FINAL PARAGRAPH OF THE HISTORY SECTION, WHERE IT BELONGS.

Explanation: This info is not a description of the product so belongs in History, not the Product /DDoS section. It also replaces two primary sources with reliable secondary sources and removes the sentence with only a primary source (Cloudflare blog).


3. Under “Products”, in the “Workers” subsection, at the end of the first sentence: In 2017 Cloudflare launched Cloudflare Workers….”.

ADD A REFERENCE TO THE SAME SENTENCE:

In 2017 Cloudflare launched Cloudflare Workers, a serverless computing platform that allows one to create entirely new applications or augment existing ones without configuring or maintaining infrastructure. Since then, the product has expanded to include Workers KV, a low-latency key-value data store, Cron Triggers for scheduling cron jobs, and additional tooling for developers to deploy and scale their code across the globe.[6]

Explanation: Sentence is identical but added a reliable source. Currently has no source.

  •  Done: However, do you have additional sources that you can provide. We should make sure this is a popular product. Boredathome101 (talk) 19:53, 26 May 2021 (UTC)[reply]

4. Under “Product” in the “Pages” subsection:

ADD

The following reference to the end of the paragraph:

The product is a Jamstack platform for front end developers to collaborate and deploy websites on Cloudflare's infrastructure of 200+ data centers worldwide.[7]

Explanation: The sentences in question didn’t have a reference. Adds reliable source.


5. In the Security and Privacy Issues section, please move the entire third paragraph,

Cloudflare is cited in reports by The Spamhaus Project, an international spam tracking organization, due to high numbers of cybercriminal botnet operations 'hosted' on Cloudflare services.[8] [9] [10] An October 2015 report found that Cloudflare provisioned 40% of SSL certificates used by phishing sites with deceptive domain names resembling those of banks and payment processors.[11]


TO THE HISTORY SECTION after the paragraph starting with “Cloudflare is cited in reports…” and ending with “... resembling those of banks and payment processors.”

Explanation: This will put the events noted in the Security and privacy issues section in chronological order.

 Not done. It's quite reasonable to lump the SSL certificate issuance with a section regarding security issues. It seems to be better placed here in that section than in the history section. — Mikehawk10 (talk) 04:10, 16 June 2021 (UTC)[reply]


6. In the Security and Privacy Issues section, in the paragraph starting “In May 2017, ProPublica….”,

AFTER the first sentence, please ADD:

Since early 2015, the disclaimer on Cloudflare’s complaint form stated that they “will notify the site owner”.[12][13][14]

THEN, AFTER THIS EXISTING SENTENCE IN THE SAME PARAGRAPH: “Cloudflare's general counsel defended the company's policies by saying it is "base constitutional law that people can face their accusers".[15]

Please ADD:


Kramer said some of those “attacking Cloudflare’s customers had their own questionable motives.”[16]

 Partly done ProPublica itself notes that the disclaimer exists in the same sentence that it says most people didn't know the info would be passed on, so it seems WP:DUE to include the content. The CNET source really doesn't do any original reporting, so it doesn't add much weight on its own, but it also support. I don't think the questionable motives is WP:DUE; it's super vague and it doesn't add much of value here. The syndicated source published in SCMP also contains advice from the CEO that I have added. — Mikehawk10 (talk) 04:10, 16 June 2021 (UTC)[reply]


ADDITIONALLY, AFTER THIS SENTENCE: “In response to the report, Cloudflare updated their abuse reporting process to provide greater control over who is notified of the complaining party.[17]

Please ADD:


Specifically, the complaint form now allows individuals to let Cloudflare know if they do not want their information shared.[18]


Explanation: The additional information, most from the ProPublica article, helps to better explain Cloudflare’s position, as per WP: VALID. It’s a different point of view on what happened documented in the same source. The last sentence provides significant additional information to understand the resolution of this contentious issue.

 Not done. I don't understand the application of WP:VALID here; there doesn't appear to be a weight concern that the suggested sentence would reasonably fix. — Mikehawk10 (talk) 04:10, 16 June 2021 (UTC)[reply]


7. In the Security and Privacy Issues section, fifth paragraph, please DELETE: On March 9, 2021, Tillie Kottmann from the hacking collective "Advanced Persistent Threat 69420" revealed to Bloomberg News that the group had gotten root shell access to Cloudflare headquarters' internal network due to a security failure in the company's camera system.[19]

Explanation: This sentence is a complete misrepresentation of the source. The article is about hackers breaching a video camera access platform for the company Verdaka. Cloudflare was one of the companies affected -- they explained in the article it only involved a handful of cameras in closed offices, which they then disconnected. The root access refers to Verdaka, not Cloudflare. This is a relatively insignificant event in the history of Cloudflare. If the decision is not to delete it, here is an accurate summarization of the source as it applies to Cloudflare:

On March 9, 2021, the hacking collective "Advanced Persistent Threat 69420" said that the group had gain root shell access to security camera data collected by the SIlicon Valley start-up Verdaka. One of the affected companies was Cloudflare. Cloudflare said the cameras were located in a small number of offices that had been closed for months; it turned off and disconnected the cameras.[20]

 Partly done. See request number 8 for details. — Mikehawk10 (talk) 04:43, 16 June 2021 (UTC)[reply]


8. In the Security and Privacy Issues section, in the last paragraph, please delete the second sentence to the end of the paragraph: This meant that they had complete access to run any commands on the network. The group also accessed video feeds from company cameras monitoring entry points and thoroughfares. Cloudflare confirmed these claims in a blog post, but disputed that the hackers would have been able to access the company's data centers from the corporate network. They also denied Kottmann's claims that they would have been able to access CEO Matthew Prince's laptop from the compromised network, stating that he was out of the office at the time.[21]

Explanation: This is all sourced to a company blog, not a WP:RS.

 Partly done. I agree that there was misrepresentation of the Bloomberg source that's WP:SYNTH-y. However, I don't think that this should be deleted wholesale; self-published sources can be used for uncontroversial self-descriptions and there are also a large number of sources about this that aren't self-published. I've made some edits to better reflect a summary of sources in the area. They don't take the form of these edits, but they addressed that the section needed to be reworked. — Mikehawk10 (talk) 04:43, 16 June 2021 (UTC)[reply]


9. In the Security and Privacy Issues section, fourth paragraph, please DELETE:

Cloudflare suffered a major outage on July 2, 2019,[22] which rendered more than 12 million websites (80% of all customers) unreachable for 27 minutes.[23] A similar outage occurred on July 17, 2020, causing a similar effect and impacting approximately the same number of sites.[24][25]

Explanation: This does not relate to security or privacy, so does not belong in this section. Doesn’t seem important enough to move the History Section. If it is moved, then this sentence within the paragraph needs to be DELETED:

“A similar outage occurred on July 17, 2020, causing a similar effect and impacting approximately the same number of sites.” because the first source, The Daily Express, can’t be used on Wikipedia WP: Perennial and the second source does not actually support this sentence - it just says there was an outage. 

 Not done The Daily Express is not deprecated, and it seems to be fine in this case where its ordinary reporting is being used to support the non-WP:REDFLAG fact that a website experienced an outage (especially where other sources are reporting the same thing). The CIA Triad, which is key to InfoSec, also includes availability. So, I don't think it needs to be deleted. — Mikehawk10 (talk) 04:49, 16 June 2021 (UTC)[reply]

Thank you for your consideration. Ryanknight24 (talk) 20:32, 13 May 2021 (UTC)[reply]

@Boredathome101: Thank you for beginning the review. I will provide more sources for Requests #1 and #3, as requested in a separate message. Thought I’d ask if you have time to review more of the requests? Many thanks for your independent review. Ryanknight24 (talk) 22:16, 2 June 2021 (UTC)[reply]


Hi, this review is still incomplete. Requests #1 and 5-9 are not reviewed.

Re: the request of User:Boredathome101 for #1 and #3, I have provided additional sources, as asked. I would just note that each statement in an article does not need to meet the WP: General Notability Guideline. Citing to one high-quality reliable source is generally the best practice. Analogous WP:GA articles include Paxata and Juniper Networks (please see the software sections).

Re #1: Here are more media sources for the Warp VPN, in addition to[26][27]”:

Re #3 Here are more media sources for Workers Unbound: TechCrunch[8]. HelpNetSecurity[9], DevClass[10], IT Pro Today[11], VentureBeat[12], IT Wire[13], SD Times[14], Forbes[15]

Thank you Ryanknight24 (talk) 17:50, 4 June 2021 (UTC)[reply]

Further Discussion for Proposals June 2021

User: Mikehawk10 and User:Boredathome101 answered some Request Edit Proposal. above. For a couple, I’d very much appreciate it if there could be a bit of discussion between editors. The first one has still not yet been evaluated at all. As disclosed above, I have a COI because I work for Cloudflare. I’ve repeated the requests below.

First Request

In my former Request #9, I asked that in the Security and Privacy Issues section, fourth paragraph, be deleted detailing outages. Since then five more outages have been added in the same paragraph. Looking at the history of repeated and frequent outages of all ISPs (not just Cloudflare) across the globe, number and frequency of outages, these appear to be routine events and therefore including every one of them seems to be WP:MILL. These common events are WP:NOTNEWS. Perhaps if any outages were especially notable for its duration or extent, then its inclusion could be warranted. As it is, listing every outage is not encyclopedic -- not every routine news event can appear. And, these sources do not say the outages are related to security and privacy -- that’s an interpretation not present in the sources, so I don’t think these would be in this section in any case. Most of these sources are not allowable in any case:

July 2, 2019 blog post from Cloudflare, supporting the second half of the first sentence.  WP: Primary

July 17, 2020 outage: The Daily Express is listed under WP:RSP as an untrustworthy source. (WP:DAILYEXPRESS), to be considered the same as WP:DailyMail a deprecated source. It should be removed (there are two sources for this outage but the second source has no details, so the whole second sentence should be removed. The reporting , whether straightforward or not, is considered by Wikipedia to be inherently untrustworthy. April 1, 2020: Thousand eyes is a blog from Cisco and not allowable as a commercial vendor primary source. WP: Primary May 3, 2021 Thousand eyes again.

Cloudflare suffered a major outage on July 2, 2019,[28] which rendered more than 12 million websites (80% of all Cloudflare's customers) unreachable for 27 minutes.[29] A similar outage occurred on July 17, 2020, with similar effect and impacting approximately the same number of sites.[30][31] Other notable outages occurred on June 24, 2019 (two hours and twenty-seven minutes),[32] April 1, 2020 (five hours and five minutes),[33] August 30, 2020 (four hours and fifty-five minutes),[34] May 3, 2021 (two hours)[35] and June 11, 2021 (one hour and five minutes).[36]

I agree that this paragraph on outages is, at a minimum, misplaced and likely unnecessary. There is no coverage from the mainstream press on these routine issues. Outages can be notable; The 8 June Fastly outage is an example. Based on the citations included, I see nothing that rises to that level here. ~Kvng (talk) 14:47, 24 June 2021 (UTC)[reply]

Second Request In Request 5, I requested the entire third paragraph In the “Security and Privacy” Issues section, be moved to History. MikeHawk101 declined. His reason seems appropriate as to not moving it, but on second review, some of the sources can’t be used because they are blogs for commercial vendors. The second source of the first sentence is a blog from a commercial vendor. The only source for the second sentence is a blog from a commercial vendor. The others are primary, but from a reputable organization (Spamhaus), so can be used with caution and not in a way that requires analysis. In this case, I suggest specifying the exact year and exact language of the most recent referenced report, which is issued every quarter, instead of making a broader interpretive statement across multiple years. I failed to find secondary sources that report on it and Cloudflare specifically, which would be preferable.

This would be deleted:


Cloudflare is cited in reports by The Spamhaus Project, an international spam tracking organization, for the high numbers of cybercriminal botnet operations hosted by Cloudflare.[37] [9] [38] An October 2015 report found that Cloudflare provisioned 40% of the SSL certificates used by typosquatting phishing sites, which use deceptive domain names resembling those of banks and payment processors to compromise Internet users' banking and other transactions.[39]

And instead, this would be inserted:


Cloudflare is cited in the Q1 2021 report by The Spamhaus Project, an international spam tracking organization, ranking it fourth among networks with the most newly observed Botnet#Command and control protocols, sometimes used by cybercriminals to control malware-infected machines.[40]


The second sentence needs to be entirely deleted because it only has a commercial blog as a source:


An October 2015 report found that Cloudflare provisioned 40% of SSL certificates used by phishing sites with deceptive domain names resembling those of banks and payment processors.[41]

Third Request

I proposed a new VPN product be added to the article in the “Products” section. It was added to the “History” section, paragraph five. I still think it properly belongs in the Products section as a new sub-section, with the sub-title “VPN”. I think a tiny description of what this product does will be helpful to less technically savvy readers, so I propose adding one additional sentence whether kept where it is or moved. .

The “History “language I propose moving is:

On April 1, 2019, Cloudflare announced a new freemium VPN service named WARP. The service would initially be available through the 1.1.1.1 mobile apps with a desktop app available later.[42] On September 25, 2019, Cloudflare released WARP to the public.[43][44] The beta for macOS and Windows was announced on April 1, 2020.[45]

My proposed new language at the bottom of Products is to create the sub-section “VPN” and add this as the last sentence to the complete paragraph moved from History:

WARP is for non-technical users and does not allow the user to choose their endpoint region or access geo-restricted content.[46][47]

Note that on4 June 2021, we provided seven additional sources, aside from those above in History and the new sentences, that discuss the new VPN product to show that it is significant. Techcrunch, Techworm, Slashgear, Cult of Mac, Fossbytes, Fast Company, Sunstar


Thank you. Ryanknight24 (talk) 22:54, 21 June 2021 (UTC)[reply]

  1. ^ Orphanides, K.G (19 October 2019). "Cloudflare 1.1.1.1 with Warp review: faster browsing, but not a real VPN". Wired UK. Conde Nast. Retrieved 20 April 2021.
  2. ^ Sharma, Mayank (7 September 2020). "Cloudflare DNS (1.1.1.1) review". TechRadar. Retrieved 20 April 2021.
  3. ^ Rahim, Zamira (September 7, 2019). "'Malicious attack' on Wikipedia causes outage in several countries". The Independent. London. Retrieved September 26, 2020.
  4. ^ "Analyzing the Wikipedia DDoS Attack". Internet and Cloud Intelligence Blog. ThousandEyes. Retrieved September 26, 2020.
  5. ^ "Wikimedia Foundation". Cloudflare. Retrieved September 26, 2020.
  6. ^ "Cloudflare creates Workers Unbound platform for serverless development". Data Center News. 3 Aug 2020. Retrieved 1 May 2021.
  7. ^ Dillet, Romain (17 December 2020). "Cloudflare launches Cloudflare Pages, a platform to deploy and host JAMstack site". Tech Crunch. Retrieved 1 May 2021.
  8. ^ "Spamhaus Botnet Threat Report Q1-2020, ISPs hosting botnet C&Cs". The Spamhaus Project. Retrieved May 1, 2020.
  9. ^ a b "Cloudflare and Spamhaus". Word to the Wise. July 16, 2017. Retrieved February 28, 2017.
  10. ^ "The Spamhaus Project". The Spamhaus Project. Retrieved September 30, 2019.
  11. ^ Edgecombe, Graham (October 12, 2015). "Certificate authorities issue SSL certificates to fraudsters". Netcraft. Retrieved October 14, 2015.
  12. ^ Schwencke, Ken (May 4, 2017). "How One Major Internet Company Helps Serve Up Hate on the Web". ProPublica. Retrieved May 6, 2017.
  13. ^ "Internet security CEO explains why harassed complainants should've used fake names". South China Morning Post. 9 May 2017. Retrieved 2 May 2021.
  14. ^ Ngo, Dong (5 May 2017). "Cloudflare helps serve up hate online, says ProPublica". Retrieved 2 May 2021.
  15. ^ Schwencke, Ken (May 4, 2017). "How One Major Internet Company Helps Serve Up Hate on the Web". ProPublica. Retrieved May 6, 2017.
  16. ^ Schwencke, Ken (May 4, 2017). "How One Major Internet Company Helps Serve Up Hate on the Web". ProPublica. Retrieved May 6, 2017.
  17. ^ Prince, Matthew (May 7, 2017). "Anonymity and Abuse Reports". The Cloudflare Blog. Retrieved August 22, 2019.
  18. ^ "Internet security CEO explains why harassed complainants should've used fake names". South China Morning Post. 9 May 2017. Retrieved 2 May 2021.
  19. ^ Turton, William (2021-03-09). "Hackers Breach Thousands of Security Cameras, Exposing Tesla, Jails, Hospitals". Bloomberg. Retrieved 2021-03-10.{{cite news}}: CS1 maint: url-status (link)
  20. ^ Turton, William (2021-03-09). "Hackers Breach Thousands of Security Cameras, Exposing Tesla, Jails, Hospitals". Bloomberg. Retrieved 2021-03-10.{{cite news}}: CS1 maint: url-status (link)
  21. ^ Graham-Cumming, John (2021-03-10). "About the March 8 & 9, 2021 Verkada camera hack". The Cloudflare Blog. Archived from the original on 2021-03-10. Retrieved 2021-03-10.
  22. ^ Cheng, Michelle. "Cloudflare shows how transparent tech companies should be". No. 15 July 2019. Quartz. Retrieved 26 April 2021.
  23. ^ Graham-Cumming, John (12 July 2019). "Details of the Cloudflare outage on July 2, 2019". Cloudflare. Retrieved 26 April 2021.
  24. ^ Dassanayake, Dion (17 July 2020). "Discord DOWN: Server status latest, connection and Cloudflare problems confirmed". Express UK. Retrieved 26 April 2021.
  25. ^ Carpenter, Nicole (17 July 2020). "Discord, Riot Games down with reported Cloudflare outage". Polygon. Retrieved 26 April 2021.
  26. ^ Orphanides, K.G (19 October 2019). "Cloudflare 1.1.1.1 with Warp review: faster browsing, but not a real VPN". Wired UK. Conde Nast. Retrieved 20 April 2021.
  27. ^ Sharma, Mayank (7 September 2020). "Cloudflare DNS (1.1.1.1) review". TechRadar. Retrieved 20 April 2021.
  28. ^ Cheng, Michelle (July 15, 2019). "Cloudflare shows how transparent tech companies should be". Quartz. Retrieved July 17, 2020.
  29. ^ Graham-Cumming, John (July 12, 2019). "Details of the Cloudflare outage on July 2, 2019". The Cloudflare Blog. Retrieved July 12, 2019.
  30. ^ Dassanayake, Dion (July 17, 2020). "Discord DOWN: Server status latest, connection and chat problems confirmed". Daily Express. Retrieved July 17, 2020.
  31. ^ Carpenter, Nicole (July 17, 2020). "Discord, Riot Games down with reported Cloudflare outage". Polygon. Retrieved July 17, 2020.
  32. ^ Perez, Sarah (2019-06-24). "Cloudflare issues affecting numerous sites on Monday". TechCrunch. Retrieved 16 June 2021. Cloudflare is having network problems this morning — and taking down a lot of its customers' sites and apps in the process. Affected companies include podcast app Overcast, chat service Discord, managed hosting provider WP Engine, eCommerce hosting provider Sonassi, public web front-end CDN service CDNJS, and many others — including the sites that rely on the web hosting or who partner with Cloudflare for their CDN service.
  33. ^ Medina, Angelique. "Why Rostelecom's Route Hijack Highlights the Need for BGP Security". ThousandEyes. On April 1, 2020, at 7:30 PM UTC, JSC Rostelecom announced a more specific /21 route to Cloudflare's services. By 12:35 PM, all illegitimate routes were withdrawn, and traffic was flowing normally to affected services.
  34. ^ Goodwin, Jazmin (2020-08-31). "Major internet outage: Dozens of websites and apps were down". CNN Business. Retrieved 16 June 2021. Cloudflare CTO Graham-Cumming claimed that CenturyLink was responsible for the outage, which took Cloudflare and its customers down with them. The outage followed a shorter one on Saturday.
  35. ^ Medina, Angelique. "Even Magic Can't Stop Internet Outages". ThousandEyes. Retrieved 16 June 2021. Today, we focused on an interesting outage that impacted Cloudflare. On May 3rd at approximately 22:00 UTC, ThousandEyes vantage points connecting to sites using Magic Transit began to detect significant packet loss at Cloudflare's network edge—with the loss continuing at varying levels, for approximately 2 hours.
  36. ^ Claburn, Thomas (2021-06-11). "Cloudflare network outage disrupts Discord, Shopify". The Register. Retrieved 16 June 2021. 'Cloudflare is aware of an issue which potentially impacts multiple customers,' the company said. Chat service Discord, reported 'connection failures in US East due to issues upstream of our service.' Shopify likewise reported service issues around 1607 UTC and said the problems were resolved by 1712 UTC.
  37. ^ "Spamhaus Botnet Threat Report Q1-2020, ISPs hosting botnet C&Cs". The Spamhaus Project. Retrieved May 1, 2020.
  38. ^ "The Spamhaus Project". The Spamhaus Project. Retrieved September 30, 2019.
  39. ^ Edgecombe, Graham (October 12, 2015). "Certificate authorities issue SSL certificates to fraudsters". Netcraft. Retrieved October 14, 2015.
  40. ^ "Spamhaus Botnet Threat Update: Q1-2021". Spamhaus. Retrieved 21 June 2021.
  41. ^ Edgecombe, Graham (October 12, 2015). "Certificate authorities issue SSL certificates to fraudsters". Netcraft. Retrieved October 14, 2015.
  42. ^ Rambo, Guilherme (April 1, 2019). "Cloudflare announces WARP: a new free VPN service for iOS". 9to5Mac. Archived from the original on April 2, 2019. Retrieved April 2, 2019.
  43. ^ Humphries, Matthew (September 26, 2019). "Cloudflare Finally Launches WARP, But It's Not a Mobile VPN". PCMAG. Retrieved September 27, 2019.
  44. ^ Security, Paul Wagenseil 2019-09-26T20:13:55Z. "WARP Promises Faster Speeds on Your Phone Without 5G, but Doesn't Quite Deliver Yet". Tom's Guide. Retrieved September 27, 2019.{{cite web}}: CS1 maint: numeric names: authors list (link)
  45. ^ Bijan Stephen (April 1, 2020). "Cloudflare's WARP VPN is launching in beta for macOS and Windows". The Verge. Retrieved September 17, 2020.
  46. ^ Orphanides, K.G (19 October 2019). "Cloudflare 1.1.1.1 with Warp review: faster browsing, but not a real VPN". Wired UK. Conde Nast. Retrieved 20 April 2021.
  47. ^ Sharma, Mayank (7 September 2020). "Cloudflare DNS (1.1.1.1) review". TechRadar. Retrieved 20 April 2021.