Talk:Fastly
Individuals with a conflict of interest, particularly those representing the subject of the article, are strongly advised not to directly edit the article. See Wikipedia:Conflict of interest. You may request corrections or suggest content here on the Talk page for independent editors to review, or contact us if the issue is urgent. |
This article was nominated for deletion on 10 April 2018. The result of the discussion was keep. |
This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||||||
|
The Wikimedia Foundation's Terms of Use require that editors disclose their "employer, client, and affiliation" with respect to any paid contribution; see WP:PAID. For advice about reviewing paid contributions, see WP:COIRESPONSE.
|
I'm a Fastly employee that has been allowed to create this article on company time so I have added a WP:PAID disclosure; however, my contributions are not at the behest of my employer, and I will cease editing the article directly if/when the article is accepted through the WP:AfC process. --Sykes83 (talk) 22:23, 21 September 2017 (UTC)
Competitors section has undue weight
[edit]This edit request by an editor with a conflict of interest was declined. The reviewer would like to request the editor with a COI attempt to discuss with editors engaged in the subject-area first. |
Hola! An editor with undisclosed COI (the CMO of a competitor) added a large competitors list to the page (and for some reason marked it as a minor edit, although I'm not sure why). The content itself seems reasonable, but it now takes up a quarter of the page giving it possibly undue weight. I'm hoping someone might consider reviewing to see if the page would be improved if the list was given less weight. -- Sykes83 (talk) 19:32, 25 June 2018 (UTC)
Reply 25-JUN-2018
[edit]The question here seems to be whether or not the person adding the information has a conflict of interest, which would require the input of editors at WP:COIN, which is where you should take your concerns. If that editor does have a COI, then their changes should be reviewed. Until that has been ascertained, I'm not sure what else can be done with content that you've described as seeming to be "reasonable". If you have references demonstrating that these are not competitors, then please provide it. That same challenge goes out to the editor who added the information, which I will note in the article with a citation needed template. spintendo 20:44, 25 June 2018 (UTC)
Proposed new section: Acquisitions
[edit]I saw someone recently added a Fastly acquisition to the History. I have recently added a list of Acquisitions to the Cloudflare page, perhaps we could also add an acquisitions section here? If anyone is interested to help, please help me compile a list... Signal Sciences, etc. Based on what I have seen on the Salesforce page (using that as a template but open to anything else), we would also want to add the month and year of the acquistiion. Nickgray (talk) 13:46, 23 December 2020 (UTC)
Submitting Acquisitions section draft for review
[edit]An impartial editor has reviewed the proposed edit(s) and asked the editor with a conflict of interest to go ahead and make the suggested changes. |
Hi there! Up front, I should disclose my conflict of interest: I'm a Fastly employee, which is why I'm using the edit request system as opposed to directly editing the company's article myself. In the post above this one, User:Nickgray suggested creating an Acquisitions section. I thought this was a good idea, so I wrote a section draft:
Extended content
|
---|
In August 2020, Fastly announced it was acquiring cybersecurity company Signal Sciences for $775 million ($200 million in cash and $575 million in stock).[1] The acquisition was made with the intention of improving Fastly's edge security, as well as the security of its applications and APIs.[1][2] At the time the purchase was announced, Signal Sciences was protecting approximately 40,000 applications and a trillion production requests per month.[1] Shortly after the announcement was made, Fastly's stock price rose by about seven percent.[2] Fastly expanded its edge cloud services through the acquisition of Fanout in March 2022. The purchase gave developers using Fastly's edge network the ability to build real-time and streaming APIs with their existing HTTP stack without having to maintain a WebSocket stack.[3] In May 2022, Fastly announced it had acquired Glitch, a web coding platform with more than 1.8 million developers.[4] Glitch apps were subsequently integrated into Fastly's edge computing services and content delivery network, and Fastly customers were given access to Glitch's development tools.[4][5] As part of the deal, Glitch CEO Anil Dash joined Fastly as its VP of developer engagement.[6] In August 2023, it was announced that Fastly had acquired Domainr, a domain search engine.[7] The Domainr API allows developers to instantly check the availability of domain names and monitor them within their own apps and services.[8] References
|
This draft covers all the company's significant acquisitions over the past few years, and explains, wherever possible, what the company Fastly acquired was known for at the time of the purchase and the way(s) that company's assets were integrated into Fastly's operation.
I don't want to get ahead of myself, but I should note that if some form of this draft is approved and an Acquisitions section is added to the article, whoever adds the text will probably also want to delete the brief passages about Signal Sciences, Glitch, and Domainr from the History section. But we can cross that bridge when we come to it. In the meantime, I invite independent editors to review my draft and let me know what they think. Thank you! Jagger at Fastly (talk) 19:20, 18 April 2024 (UTC)
- I'm going to ping User:QuietCicada, since they recently made a helpful edit to the article. I want to be clear: no obligation on your part, Cicada. I know you're editing on your own time. Just checking to see if you'd like to review this request. Thanks! Jagger at Fastly (talk) 19:43, 2 May 2024 (UTC)
- @Jagger at Fastly:, I honestly hate having acquisition sections. The information is better formatted under history, creating subheadings based on years if necessary. Let me know if you would like me to take a closer look as I would be glad to clean up and implement what can be done. --CNMall41 (talk) 04:02, 13 May 2024 (UTC)
- Hey User:CNMall41, this is very helpful feedback. I think I've got an idea about what to do, but it'll take a bit of work on my end. I'll be back once that's done. Thank you for getting involved and talk soon. Jagger at Fastly (talk) 20:26, 15 May 2024 (UTC)
- Returning to this thread to propose a full History section revision, which contains a subsection for Acquisitions, which I believe is a good idea because there are quite a few of them. (But I'm open to changing that, if editors think there's a better way!) In addition to gathering the acquisitions under their own heading, I've done some light reorganizing and added information about a few notable events in the company's history.
- This draft is lengthy, so to make things a little easier for editors, I'm going to use the comparison function. Click the dropdown below to see my History draft contrasted against the current section:
Current History vs. History Draft
| ||||
---|---|---|---|---|
References
|
- Here is what the History would look like if my draft were accepted with no alterations:
Revised History
|
---|
Fastly was founded in 2011 by the Swedish-American entrepreneur Artur Bergman, previously chief technical officer at Wikia.[1][2] In June 2013, Fastly raised $10 million in Series B funding.[3] In September 2014, Fastly raised a further $40 million in Series C funding,[4] followed by a $75 million Series D round in August 2015.[5] In September 2015, Google partnered with Fastly and other content delivery network providers to offer services to its users.[6] In April 2017, Fastly launched its edge cloud platform along with image optimization, load balancing, and a web application firewall.[7][8] Fastly raised $50 million in funding in April 2017,[9] and another $40 million in July 2018.[10] The company filed for an initial public offering (IPO) in April 2019 and debuted on the New York Stock Exchange on May 17, 2019.[11][12] In February 2020, Bergman stepped down as CEO and assumed the role of chief architect and executive chairperson; Joshua Bixby took over the CEO role.[13] In June 2021, Ronald W. Kisling, previously employed by Alphabet as the CFO of the Fitbit division, was hired to serve as Fastly's CFO, succeeding Adriel Lares. He assumed the position in August 2021.[14][15] In August 2022, Todd Nightingale, previously employed by Cisco as Executive Vice President of Enterprise Networking and Cloud business, was hired to serve as Fastly's CEO, succeeding Joshua Bixby.[16] That same year, Fastly worked with Apple and Google to create private access tokens meant to replace CAPTCHA as a method for apps and websites to differentiate human users from bots.[17] In March 2023, Fastly won a contract to develop an oblivious HTTP relay intended to help Google serve ads to users without the use of third-party cookies.[18] Fastly has been involved in several efforts to support open source projects and internet infrastructure. In 2019, the company co-founded the Bytecode Alliance alongside Mozilla, Red Hat, and Intel.[19] This group is a non-profit that seeks to expand the utility and security of WebAssembly.[20][19] In April 2021, Fastly joined the MACH Alliance, which promotes the use of open IT ecosystems.[21] In November 2022, the company launched its Fast Foward initiative.[22] Through this initiative, it committed $50 million in free services toward the development of open source projects such as the H2O web server.[23][24] Acquisitions[edit]In August 2020, Fastly announced it was acquiring cybersecurity company Signal Sciences for $775 million ($200 million in cash and $575 million in stock).[25] The acquisition was made with the intention of improving Fastly's edge security, as well as the security of its applications and APIs.[25][26] At the time the purchase was announced, Signal Sciences was protecting approximately 40,000 applications and a trillion production requests per month.[25] Shortly after the announcement was made, Fastly's stock price rose by about seven percent.[26] Fastly expanded its edge cloud services through the acquisition of Fanout in March 2022. The purchase gave developers using Fastly's edge network the ability to build real-time and streaming APIs with their existing HTTP stack without having to maintain a WebSocket stack.[27] In May 2022, Fastly announced it had acquired Glitch, a web coding platform with more than 1.8 million developers.[28] Glitch apps were subsequently integrated into Fastly's edge computing services and content delivery network, and Fastly customers were given access to Glitch's development tools.[28][29] As part of the deal, Glitch CEO Anil Dash joined Fastly as its VP of developer engagement.[30] In August 2023, it was announced that Fastly had acquired Domainr, a domain search engine.[31] The Domainr API allows developers to instantly check the availability of domain names and monitor them within their own apps and services.[32] References
|
- I invite User:CNMall41 to take a look at this; I hope it's more in line with their thinking about how the article should be structured. Other independent editors may jump in as well. Thank you! Jagger at Fastly (talk) 19:27, 22 May 2024 (UTC)
- Per a chat I just had with User:CNMall41 on their user Talk page, I'm going to revise my proposal further, unifying the whole History section and sprinkling the acquisitions wherever they fit in chronologically. Here's a comparison of the current History vs. my draft:
Current History vs. History Draft (version 2)
| ||||
---|---|---|---|---|
References
|
- And here's what my draft would look like if it were added to the article without any changes:
Revised History (version 2)
|
---|
Fastly was founded in 2011 by the Swedish-American entrepreneur Artur Bergman, previously chief technical officer at Wikia.[1][2] In June 2013, Fastly raised $10 million in Series B funding.[3] In September 2014, Fastly raised a further $40 million in Series C funding,[4] followed by a $75 million Series D round in August 2015.[5] In September 2015, Google partnered with Fastly and other content delivery network providers to offer services to its users.[6] In April 2017, Fastly launched its edge cloud platform along with image optimization, load balancing, and a web application firewall.[7][8] Fastly raised $50 million in funding in April 2017,[9] and another $40 million in July 2018.[10] The company filed for an initial public offering (IPO) in April 2019 and debuted on the New York Stock Exchange on May 17, 2019.[11][12] In February 2020, Bergman stepped down as CEO and assumed the role of chief architect and executive chairperson; Joshua Bixby took over the CEO role.[13] In August 2020, Fastly announced it was acquiring cybersecurity company Signal Sciences for $775 million ($200 million in cash and $575 million in stock).[14] The acquisition was made with the intention of improving Fastly's edge security, as well as the security of its applications and APIs.[14][15] At the time the purchase was announced, Signal Sciences was protecting approximately 40,000 applications and a trillion production requests per month.[14] Shortly after the announcement was made, Fastly's stock price rose by about seven percent.[15] In June 2021, Ronald W. Kisling, previously employed by Alphabet as the CFO of the Fitbit division, was hired to serve as Fastly's CFO, succeeding Adriel Lares. He assumed the position in August 2021.[16][17] Fastly expanded its edge cloud services through the acquisition of Fanout in March 2022. The purchase gave developers using Fastly's edge network the ability to build real-time and streaming APIs with their existing HTTP stack without having to maintain a WebSocket stack.[18] In May 2022, Fastly announced it had acquired Glitch, a web coding platform with more than 1.8 million developers.[19] Glitch apps were subsequently integrated into Fastly's edge computing services and content delivery network, and Fastly customers were given access to Glitch's development tools.[19][20] As part of the deal, Glitch CEO Anil Dash joined Fastly as its VP of developer engagement.[21] In August 2022, Todd Nightingale, previously employed by Cisco as Executive Vice President of Enterprise Networking and Cloud business, was hired to serve as Fastly's CEO, succeeding Joshua Bixby.[22] That same year, Fastly worked with Apple and Google to create private access tokens meant to replace CAPTCHA as a method for apps and websites to differentiate human users from bots.[23] In March 2023, Fastly won a contract to develop an oblivious HTTP relay intended to help Google serve ads to users without the use of third-party cookies.[24] In August of the same year, it was announced that Fastly had acquired Domainr, a domain search engine.[25] The Domainr API allows developers to instantly check the availability of domain names and monitor them within their own apps and services.[26] Fastly has been involved in several efforts to support open source projects and internet infrastructure. In 2019, the company co-founded the Bytecode Alliance alongside Mozilla, Red Hat, and Intel.[27] This group is a non-profit that seeks to expand the utility and security of WebAssembly.[28][27] In April 2021, Fastly joined the MACH Alliance, which promotes the use of open IT ecosystems.[29] In November 2022, the company launched its Fast Foward initiative.[30] Through this initiative, it committed $50 million in free services toward the development of open source projects such as the H2O web server.[31][32] References
|
- Alright, I think this draft is in a good place now, but it's obviously not up to me to decide. If anybody has feedback or further thoughts, please let me know! Thank you, Jagger at Fastly (talk) 22:57, 29 May 2024 (UTC)
- Since this request has been dormant for two months now, I'm going to invite User:CNMall41 to revisit it. I'll also tag in a couple editors who have made helpful contributions to the Fastly article in the past: User:EastThermopolis and User:TollyH. Obviously, none of these independent editors should feel obligated to review what's above. I'm just searching for folks who might be interested. Thanks in advance to anyone who takes a look! Jagger at Fastly (talk) 15:15, 26 July 2024 (UTC)
- Alright, I think this draft is in a good place now, but it's obviously not up to me to decide. If anybody has feedback or further thoughts, please let me know! Thank you, Jagger at Fastly (talk) 22:57, 29 May 2024 (UTC)
- Go ahead: I have reviewed these proposed changes and suggest that you go ahead and make the proposed changes to the page. Please use your most recent draft; thank you for your patience. Rusalkii (talk) 06:04, 28 August 2024 (UTC)
Submitting Operation section draft for editor review
[edit]This edit request by an editor with a conflict of interest has now been answered. |
Hello again! It seems like my request above has stalled since I last revised it. I worry that it's gotten a little too complicated for new editors to wrap their heads around. So I'm going to leave it be for a bit and move ahead by proposing a few updates to the Operation section. There are some new aspects of the company's services that aren't currently covered in this section, so I did some research and did my best to substantiate new claims. I also sought to fix some existing sourcing issues by trimming content and locating a handful of new reliable sources. Below, you can see the current section vs. my draft:
Current Operation vs. Operation Draft
| ||||
---|---|---|---|---|
References
|
And here is what the section would look like if all my suggested edits were made:
Revised Operation section
|
---|
Fastly's CDN service follows the reverse proxy model, routing all website traffic through their own servers instead of providing a 'cdn.mydomain.com' address to store site-specific files. It then fetches content from the point of presence nearest to the location of the requesting user. Content is not directly uploaded to their servers, rather it is pulled periodically from the origin server and cached in order to reduce the time required for an end-user to access the content.[1] Fastly uses artificial intelligence to improve the rate at which content is delivered by its network.[2] Fastly supports the UDP-based HTTP/3 protocol, as well as DRM enabled content, encryption and secure tokens to restrict media access.[1][3] On 8 June 2021, Fastly reported problems with their CDN service which caused many major websites, such as Reddit, gov.uk, Twitch, Spotify and Amazon, along with major news sources such as The New York Times, The Guardian, CNN and the BBC, to become unavailable.[4] It also affected certain parts of other major websites, such as the servers hosting the emojis used by Twitter, resulting in them becoming inaccessible.[5] The outage was resolved by Fastly after a few hours. Fastly reported that the cause of the outage was a software bug triggered by a specific user configuration.[6][7] Fastly has since stated that it has enacted several resiliency and redundancy efforts intended to protect against future outages.[8][9] In November 2022, the company expanded its offering of edge observability tools. These tools allow Fastly users to organize real-time and historical data to gauge the function of their edge computing networks.[10] In March 2023, Fastly made all of its network services and web application security products available to its partners. Previously, some of the company's partners had only been able to sell specific Fastly products, such as its web application firewall.[11] References
|
As ever, I'm happy to discuss my proposed edits with independent editors and adjust the copy above as needed. Thanks! Jagger at Fastly (talk) 20:48, 26 June 2024 (UTC)
- The MarketBeat analysis feels like a regurgitation of the Fastly earnings call, I would avoid using this source.
- The 2021 outage seems to be given undue weight, compare with Amazon Web Services#Significant service outages. I don't think paring this down would be biased towards Fastly.
- The last paragraph on edge observability and channel partner programs doesn't belong on Wikipedia. Please consider if the majority of our readers are interested in the availability of Fastly products to channel partners or even can comprehend that sentence. Brandon (talk) 23:50, 6 July 2024 (UTC)
- Hey, User:Brandon! Based on your feedback, I've made a few adjustments to the draft. I replaced the MarketBeat article with a Silicon Angle one that I hope is a little stronger. I also trimmed the outage paragraph slightly. In the last paragraph, I got rid of the edge observability sentence but kept the passage about Fastly's partner program. This was a rather significant expansion of our services and I think it's written in a way that's legible to a general audience. Your mileage may vary, though.
- Here's the revised section draft:
Operation (version 2)
|
---|
Fastly's CDN service follows the reverse proxy model, routing all website traffic through their own servers instead of providing a 'cdn.mydomain.com' address to store site-specific files. It then fetches content from the point of presence nearest to the location of the requesting user. Content is not directly uploaded to their servers, rather it is pulled periodically from the origin server and cached in order to reduce the time required for an end-user to access the content.[1] Fastly uses artificial intelligence to improve the rate at which content is delivered by its network.[2] Fastly supports the UDP-based HTTP/3 protocol, as well as DRM enabled content, encryption and secure tokens to restrict media access.[1][3] On 8 June 2021, Fastly reported problems with their CDN service which caused many major websites, such as Reddit, gov.uk, and Amazon, along with major news sources such as The New York Times, The Guardian, and the BBC, to become unavailable.[4] The outage was resolved by Fastly after a few hours. Fastly reported that the cause of the outage was a software bug triggered by a specific user configuration.[5][6] Fastly has since stated that it has enacted several resiliency and redundancy efforts intended to protect against future outages.[7][8] In March 2023, Fastly made all of its network services and web application security products available to its partners. Previously, some of the company's partners had only been able to sell specific Fastly products, such as its web application firewall.[9] References
|
- Really appreciate your help with this. If you've got additional thoughts, please let me know! Jagger at Fastly (talk) 00:23, 9 July 2024 (UTC)
- Done, thank you for your patience. I have removed one additional sentence, on "resiliency and redundancy efforts" post outage. Of the two sources given, one is the company itself and the other is essentially an interview with the CEO. For something like this, I'd want to see independent coverage - otherwise, it's just the normal "we are taking measures to fix this" type verbiage any company is going to release after a major incident. Rusalkii (talk) 19:45, 18 August 2024 (UTC)
- The last sentence of the first paragraph is highly misleading, as the source [1] describes what amounts to a Web cache for language-model APIs. The phrasing of the sentence implies that Fastly is using AI to improve network transfer rate, which is an unsourced claim. RhubarbKnife (talk) 14:53, 4 October 2024 (UTC)
- Done, thank you for your patience. I have removed one additional sentence, on "resiliency and redundancy efforts" post outage. Of the two sources given, one is the company itself and the other is essentially an interview with the CEO. For something like this, I'd want to see independent coverage - otherwise, it's just the normal "we are taking measures to fix this" type verbiage any company is going to release after a major incident. Rusalkii (talk) 19:45, 18 August 2024 (UTC)
- Really appreciate your help with this. If you've got additional thoughts, please let me know! Jagger at Fastly (talk) 00:23, 9 July 2024 (UTC)
Section on June 8 Outage
[edit]The general public would be most aware of Fastly though the June 8 outage, which is the only time Fastly made headlines in major news outlets. Considering the severity and impact of the outage, which made international headlines in major media outlets, I think this deserves a dedicated section. At the very least it should be a subheading in the history.
It appears that references to the June 8 outage have been gradually erased from this article over time, which I suspect may be due to editors with undeclared conflicts of interest (COI).
Considering that this event was notable enough to be covered by several major news sites, as well as industry news sites and market news sites, it is very clearly one of the most notable events in the company's history. Omitting this event from the "History" section is suspiciously biased. The three sentences in the "Operation" section do not provide adequate detail about this event.
If we compare with Amazon Web Services#Significant service outages, perhaps the best compromise here would be a "Significant service outages" subsection within the "History" page, which right now seems to be written for investors rather than the general public, who would be more interested in the events that they remember experiencing firsthand.
Sources on the June 8 Outage:
- Fastly: https://www.fastly.com/blog/summary-of-june-8-outage/
- BBC: https://www.bbc.co.uk/news/technology-57413224
- The Guardian: https://www.theguardian.com/technology/2021/jun/09/fastly-says-single-customer-triggered-bug-that-caused-mass-outage
- CNBC: https://www.cnbc.com/2021/06/08/fastly-outage-internet-what-happened.html
- Al Jazeera: https://www.aljazeera.com/economy/2021/6/8/major-media-websites-go-down-worldwide
- The Register: https://www.theregister.com/2021/08/05/fastly_ceo_outage/
- Cisco ThousandEyes: https://www.thousandeyes.com/blog/inside-the-fastly-outage-analysis-and-lessons-learned
- Kentik: https://www.kentik.com/analysis/fastly-outage-knocks-major-websites-offline/
- S&P Global: https://www.spglobal.com/marketintelligence/en/news-insights/latest-news-headlines/fastly-outage-leads-global-internet-disruptions-for-week-of-june-5-64990984 82.36.161.73 (talk) 15:59, 3 October 2024 (UTC)
- Can some independent editors and wikipedians kindly review above ask as well as recent revert from same user @82.36.161.73 , for possible conflict of WP:NPOV ...
- The revert overlaps with apparent conditions of WP:PROMOTION but would not a template/improvement edit to reconsider MOS:PUFFERY be more appropriate than completely deleting said content? Nisingh.8 (talk) 18:23, 3 October 2024 (UTC)
- The content which I deleted was promotional material for a recently announced minor feature. It is my opinion that this could be bias through undue weight WP:UNDUE. Rewording this promotional content would not address the issue of weight WP:WEIGHT.
- It is my opinion that the international media coverage of the June 8th outage is evidence of the significant public interest in this event WP:SUBSTANTIAL.
- The history section reads as a timeline of significant events, so the omission of the event which was most widely covered in international media could be misleading, even when included in a later section WP:STRUCTURE. 82.36.161.73 (talk) 21:46, 3 October 2024 (UTC)
- C-Class AfC articles
- AfC submissions by date/08 April 2018
- Accepted AfC submissions
- C-Class Internet articles
- Low-importance Internet articles
- WikiProject Internet articles
- C-Class company articles
- Low-importance company articles
- WikiProject Companies articles
- Talk pages of subject pages with paid contributions
- Declined requested edits
- Answered requested edits
- Implemented requested edits