more than 75% of the US stock market now traded via algorithms. Quantitative strategies have become seen as the active manager’s way of generating higher returns to outperform the growing amount of capital moving into passive investing strategies. This has been seen in the growth of the number of quant funds over the years (from ~10% of the market in 2007 to ~17% in June 2017), as even more fundamental hedge funds are turning to quants or platforms that enable non-technical PMs to run their strategies or ideas through algorithms.

The likelihood of another sudden market crash led by automated trading is almost inevitable. As these markets become even more interconnected and more and more traders or funds are using automated trading strategies, the effects of such a crash will not be contained just within a small community of hedge fund managers as it was during the Quant Quake. Instead, it will be felt by all investors and funds, and throughout the broader market.

…and beyond
The shift to automated trading isn’t just happening within the hedge fund community. In March 2017, Blackrock announced a move to consolidate many of its actively managed mutual funds and rely more on stock picking algorithms, triggering other traditional asset managers to follow suit. The has created a more populous network that relies on quantitative strategies for returns.

Copycats continue, bringing amateurs along
If in 2007, part of the issue was that too many of the trading strategies were too similar, has this risk decreased at all? To the contrary, there are more copy cats today than there were in 2007. Furthermore, there are more investors that are not as quantitatively savvy using various platforms or solutions that allow them to enact quantitative strategies as if they were. This also means that there are more investors whose primary focus, or at least significant focus, may be other asset classes, inherently linking quantitative investing to the rest of the financial market.

Regulators come up empty
It took the SEC four months to issue its report on the cause of the Flash Crash in 2010, and it is still generally unknown which fund was the initial trigger for the Quant Quake in 2007. This issue of the ‘black box’ for quant algorithms has been, at least for now, accepted. So, when a large downturn occurs, these quant strategies begin losing money, and investors want to understand what went wrong, will we still be okay with not knowing what is driving the decisions of our algorithms?

Regulators have made some attempts to protect against large-scale market fluctuations which are exaggerated by these algorithms. However, initiatives such as circuit breakers are just superficial solutions. We saw this two years ago when markets went into free fall and circuit breakers were tripped more than 1,300 times and didn’t help share prices of major companies from dropping tens of percentage points in just minutes.

While regulation and more market oversight could help to lessen the risk of a bigger, more widespread Quant Quake, a key issue is transparency. As markets become more complex and interconnected, we need to make sure to understand how they are connected and how actions in one market may or may not impact another.

The equity market risks are now amplified
While easier said than done, some of the features that have defined the equity market since the Great Recession have only amplified flash crash risks. For most of the last decade, share buybacks have been the main source of capital inflow into the US equity market. On top of that, the quiet IPO market alongside an active M&A market have also led to a decrease in the number of publicly traded companies. The combination of these trends means that there are fewer shares outstanding in the market, which in turn means that even smaller buy and sell orders can lead to exaggerated swings.

To me, this market set up sounds familiar, and doesn’t sound as though we are far off from another Quant Quake if a significant downturn in the market occurs.

Why haven’t we learned? Are events like the Quant Quake now just inevitable? Or are we just not taking the necessary steps to mitigate the risks?

The obvious, but uncool, answer: regulation
As someone whose first real awakening to economics and finance was the collapse of Lehman Brothers, there are takeaways from the causes of the Great Recessions that can, and should, be useful in mitigating the potential impact of another Quant Quake.

Much of Wall Street lives under the assumption that less is more in terms of oversight. Ten years ago, the industry’s attitude was that it didn’t matter if anyone understood the quality of the mortgages packaged into CDOs. Now, it’s as if it no one cares that few understand how algorithms make trading decisions. As our markets and the assets in it become more complex and interconnected, there are fewer and fewer people involved, even those in the weeds making trades on a daily basis, that really understand.

An analogy from structural engineering world comes to mind. If a large crowd of people on a stadium balcony begins to jump in synch, no matter how strong the balcony is, at some point it will begin to bend and recoil. When this up and down motion inevitably becomes too extreme for the material with which the balcony was made to handle, it may collapse and fail.

The past decade’s market volatility is a similarly exaggerated movement. With the growing number of funds crowding into quantitative strategies, without the right oversight, it’s not too far off to believe that sooner or later, the structure that is the US equity market may too see swings that are too extreme, bringing it to the point of collapse. This is not to say this scenario is necessarily destiny, however, action is needed to mitigate these risks, decrease the likelihood of such a downturn, and further support the market.

Jillian Williams is an Investment Associate at Anthemis.


What’s Changed in the 10 Years Since Quant Quake? Not Much. was originally published in #hackingfinance on Medium, where people are continuing the conversation by highlighting and responding to this story.

"> What’s Changed in the 10 Years Since Quant Quake? Not Much. - Bank Automation News
Bank Automation News

No products in the cart.

Subscribe
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
Log In
No Result
View All Result
  • AI
  • Business Banking
  • Core
  • Cloud
  • Payments
  • Retail Banking
  • Risk & Security
Bank Automation News
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
BAN PLUS
Log In
No Result
View All Result
Bank Automation News
No Result
View All Result

What’s Changed in the 10 Years Since Quant Quake? Not Much.

Jillian WilliamsbyJillian Williams
August 10, 2017
in Archive
Reading Time: 6 mins read
0
Share on Facebook

Ten years ago today, in the months leading to the start of the global recession, the ‘Quant Quake’ of August 10, 2007 shook Wall Street. The Quant Quake saw some of the top quant funds in the US, including those belonging to AQR and Goldman Sachs, lose billions of dollars in a matter of weeks. Many of the funds at the time were highly correlated, and as one firm began selling its equity positions, that created a seemingly unstoppable domino effect.

At the time, few understood what caused these algorithms to falter. However, looking back, it’s clear that some of the inherent risks that caused billions in losses were overlooked.

While the global recession and mortgage market meltdown weren’t “expected,” the idea that drastic downturns in other parts of the market — such as the mortgage or credit markets — would have no impact on the stock market and the performance of quants in hindsight look pretty naïve. And with the success of quant strategies, one should have, or at least could have, expected a wide array of copy cat managers would come along trying to cash in.

But what’s changed since the Quant Crash of 2007? Have we found ways to protect the market from unexpected and extreme downturns driven, at least in part, by quants? Have funds or fund managers found ways to better understand their algorithms?

It doesn’t seem like it. Only three years after Quant Quake, another notable incident of huge market fluctuations driven by algorithms occurred: The Flash Crash of 2010, in which trillions of dollars were lost from the US equity markets, only to be mostly recovered, all within about 36 minutes.

Looking back over the past ten years, it’s clear that not only have we not solved the problems that created Quant Quake, but the financial markets are more vulnerable than ever to another fast, unexpected, quant-driven fluctuation. Here’s why.

The rise of automated trading in hedge funds
Since 2007, the usage of automated trading strategies has only increased with more than 75% of the US stock market now traded via algorithms. Quantitative strategies have become seen as the active manager’s way of generating higher returns to outperform the growing amount of capital moving into passive investing strategies. This has been seen in the growth of the number of quant funds over the years (from ~10% of the market in 2007 to ~17% in June 2017), as even more fundamental hedge funds are turning to quants or platforms that enable non-technical PMs to run their strategies or ideas through algorithms.

The likelihood of another sudden market crash led by automated trading is almost inevitable. As these markets become even more interconnected and more and more traders or funds are using automated trading strategies, the effects of such a crash will not be contained just within a small community of hedge fund managers as it was during the Quant Quake. Instead, it will be felt by all investors and funds, and throughout the broader market.

…and beyond
The shift to automated trading isn’t just happening within the hedge fund community. In March 2017, Blackrock announced a move to consolidate many of its actively managed mutual funds and rely more on stock picking algorithms, triggering other traditional asset managers to follow suit. The has created a more populous network that relies on quantitative strategies for returns.

Copycats continue, bringing amateurs along
If in 2007, part of the issue was that too many of the trading strategies were too similar, has this risk decreased at all? To the contrary, there are more copy cats today than there were in 2007. Furthermore, there are more investors that are not as quantitatively savvy using various platforms or solutions that allow them to enact quantitative strategies as if they were. This also means that there are more investors whose primary focus, or at least significant focus, may be other asset classes, inherently linking quantitative investing to the rest of the financial market.

Regulators come up empty
It took the SEC four months to issue its report on the cause of the Flash Crash in 2010, and it is still generally unknown which fund was the initial trigger for the Quant Quake in 2007. This issue of the ‘black box’ for quant algorithms has been, at least for now, accepted. So, when a large downturn occurs, these quant strategies begin losing money, and investors want to understand what went wrong, will we still be okay with not knowing what is driving the decisions of our algorithms?

Regulators have made some attempts to protect against large-scale market fluctuations which are exaggerated by these algorithms. However, initiatives such as circuit breakers are just superficial solutions. We saw this two years ago when markets went into free fall and circuit breakers were tripped more than 1,300 times and didn’t help share prices of major companies from dropping tens of percentage points in just minutes.

While regulation and more market oversight could help to lessen the risk of a bigger, more widespread Quant Quake, a key issue is transparency. As markets become more complex and interconnected, we need to make sure to understand how they are connected and how actions in one market may or may not impact another.

The equity market risks are now amplified
While easier said than done, some of the features that have defined the equity market since the Great Recession have only amplified flash crash risks. For most of the last decade, share buybacks have been the main source of capital inflow into the US equity market. On top of that, the quiet IPO market alongside an active M&A market have also led to a decrease in the number of publicly traded companies. The combination of these trends means that there are fewer shares outstanding in the market, which in turn means that even smaller buy and sell orders can lead to exaggerated swings.

To me, this market set up sounds familiar, and doesn’t sound as though we are far off from another Quant Quake if a significant downturn in the market occurs.

Why haven’t we learned? Are events like the Quant Quake now just inevitable? Or are we just not taking the necessary steps to mitigate the risks?

The obvious, but uncool, answer: regulation
As someone whose first real awakening to economics and finance was the collapse of Lehman Brothers, there are takeaways from the causes of the Great Recessions that can, and should, be useful in mitigating the potential impact of another Quant Quake.

Much of Wall Street lives under the assumption that less is more in terms of oversight. Ten years ago, the industry’s attitude was that it didn’t matter if anyone understood the quality of the mortgages packaged into CDOs. Now, it’s as if it no one cares that few understand how algorithms make trading decisions. As our markets and the assets in it become more complex and interconnected, there are fewer and fewer people involved, even those in the weeds making trades on a daily basis, that really understand.

An analogy from structural engineering world comes to mind. If a large crowd of people on a stadium balcony begins to jump in synch, no matter how strong the balcony is, at some point it will begin to bend and recoil. When this up and down motion inevitably becomes too extreme for the material with which the balcony was made to handle, it may collapse and fail.

The past decade’s market volatility is a similarly exaggerated movement. With the growing number of funds crowding into quantitative strategies, without the right oversight, it’s not too far off to believe that sooner or later, the structure that is the US equity market may too see swings that are too extreme, bringing it to the point of collapse. This is not to say this scenario is necessarily destiny, however, action is needed to mitigate these risks, decrease the likelihood of such a downturn, and further support the market.

Jillian Williams is an Investment Associate at Anthemis.


What’s Changed in the 10 Years Since Quant Quake? Not Much. was originally published in #hackingfinance on Medium, where people are continuing the conversation by highlighting and responding to this story.

Tags: finance
Previous Post

LendingRobot, NSR Invest Merge to Create New Roboadvisor

Next Post

Credit Cards Still Have Too Many Fees

Related Posts

Image by CanStock
Archive

Blend Labs integrates acquisition’s mortgage automation process

August 20, 2021
Photo by CanStock
Archive

Chilean fintech looks for slice of giant money transfers market

August 5, 2021
Image by CanStock
Risk & Security

Listen: How banks can protect themselves against cybersecurity risks

August 3, 2021
Next Post

Credit Cards Still Have Too Many Fees

Please login to join discussion

Stay Informed with Our Newsletters

EMERGING FINTECH DIRECTORY

Emerging Fintech Directory

The Buzz Podcast

RETAIL BANKING

Huntington Bank’s new branch in Spartanburg

Huntington Bank resolves outage

May 7, 2025
bank

Barclays, Banco Santander, Lloyds plan product expansion

May 5, 2025
satisfactiin

Online banks lead FIs in customer satisfaction

May 2, 2025

SPONSORED

Just Released! 2025 Strategy Benchmark

May 1, 2025

Leverage Treasury Management to Turn Fraud Prevention Into a Strategic, Revenue-Generating Opportunity

April 1, 2025

A growth mindset in banking requires AI

March 27, 2025
  • About Us
  • Help Center
  • Contact Us
  • Privacy Terms
  • ADA Compliance
  • Advertise

 Manage Cookie Consent

Connect

twitter linkedin podcast podcast podcast
© 2025 Royal Media
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

THIS WEBSITE USES COOKIES

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “I CONSENT”, you consent to the use of ALL the cookies.

Cookie settingsI CONSENT

Review our Cookie Policies
.
Manage Cookie Consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
__cfruidsessionCloudflare sets this cookie to identify trusted web traffic.
__RequestVerificationTokensessionThis cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck1 yearThis cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
34f6831605sessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
a64cedc0bfsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ak_bmsc2 hoursThis cookie is used by Akamai to optimize site security by distinguishing between humans and bots
ARRAffinitysessionARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.
ARRAffinitySameSitesessionThis cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
AWSELBsessionAssociated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
bm_sz4 hoursThis cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
cf_ob_infopastThe cf_ob_info cookie is set by Cloudflare to provide information on HTTP Status Code returned by the origin web server, the Ray ID of the original failed request and the data center serving the traffic.
cf_use_obpastCloudflare sets this cookie to improve page load times and to disallow any security restrictions based on the visitor's IP address.
CONCRETE5sessionThis cookie is set by the provider Concrete5 web content management system. This is a necessary cookie used for maintaining the user session between pages.
connect.sid1 monthThis cookie is used for authentication and for secure log-in. It registers the log-in information.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
cookiesession11 yearThis cookie is set by the Fortinet firewall. This cookie is used for protecting the website from abuse.
crmcsrsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ep20130 minutesThis cookie is set by Wufoo for load balancing, site traffic and preventing site abuse.
JSESSIONIDsessionThe JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
LS_CSRF_TOKENsessionCloudflare sets this cookie to track users’ activities across multiple websites. It expires once the browser is closed.
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
sxa_sitesessionThis cookie is used to identify the webiste visitor's session state across page requests on server.
ts3 yearsPayPal sets this cookie to enable secure transactions through PayPal.
ts_c3 yearsPayPal sets this cookie to make safe payments through PayPal.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wordpress_test_cookiesessionThis cookie is used to check if the cookies are enabled on the users' browser.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_zcsr_tmpsessionZoho sets this cookie for the login function on the website.
663a60c55dsessionThis cookie is related to Zoho (Customer Service) Chatbox
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
e188bc05fesessionThis cookie is set in relation to Zoho Campaigns
geosessionThis cookie is used for identifying the geographical location by country of the user.
iamcsrsessionZoho (Customer Support) sets this cookie and is used for tracking visitors (for performance purposes)
langsessionLinkedIn sets this cookie to remember a user's language setting.
languagesessionThis cookie is used to store the language preference of the user.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
optimizelyEndUserId1 yearOptimizely uses this cookie to store a visitor's unique identifier which is a combination of a timestamp and a random number. Different variations of web parts are shown to users that optimizes the website's user experience.
tableau_localesessionTableau uses this cookie to determine the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
AWSELBCORS20 minutesThis cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThe __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
ajs_anonymous_idneverThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
ajs_group_idneverThis cookie is set by Segment to track visitor usage and events within the website.
ajs_user_idneverThis cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability.
browser_id5 yearsThis cookie is used for identifying the visitor browser on re-visit to the website.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
sid1 yearThe sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time.
uid1 yearThis is a Google UserID cookie that tracks users across various website segments.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
WMF-Last-Access1 month 21 hours 5 minutesThis cookie is used to calculate unique devices accessing the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_dc_gtm_UA-1038974-41 minuteUsed to help identify the visitors by either age, gender, or interests by DoubleClick - Google Tag Manager.
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_pxhdpastUsed by Zoominfo to enhance customer data.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextIdneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requestsneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
049fc2ef5beb27056b07d9e4c4d13fd3sessionNo description
akaalb_http_misc_subssessionNo description
AnalyticsSyncHistory1 monthNo description
BIGipServermsocu-web-2-rr.webfarm.ms.com.10882sessionNo description
bm_misessionNo description available.
CX_4061522881 yearNo description
DCID20 minutesNo description
debugneverNo description available.
DrupalVisitorMobilesessionNo description available.
ep2033 monthsNo description available.
frbatlanta#langsessionNo description
geo_info1 yearNo description available.
GoogleAdServingTestsessionNo description
li_gc2 yearsNo description
loglevelneverNo description available.
loom_anon_commentsessionNo description available.
loom_referral_videosessionNo description
mkjs_group_idneverNo description available.
mkjs_user_idneverNo description available.
MorganStanley.ClientServ.Common.IPZipAccess.IPZipCookie.DEFAULT_COOKIE_NAMEpastNo description
NSC_us_nbsl-83+63+21+25-91sessionNo description
nyt-a1 yearThis cookie is set by the provider New York Times. This cookie is used for saving the user preferences. It is used in context with video and audio content.
nyt-gdpr6 hoursNo description available.
nyt-purr1 yearNo description available.
OCC_Encrypted_CookiesessionNo description
polleverywhere_session_id14 daysNo description
ppnet_2020sessionNo description available.
ppnet_2777sessionNo description available.
reuters-geosessionNo description
shell#langsessionNo description
smcx_0_last_shown_atsessionNo description available.
tableau_public_negotiated_localesessionNo description available.
vary1 monthNo description
www#langsessionNo description
X-Vive-CountrysessionNo description
xn_uuid1 monthNo description
Save & Accept
Powered by CookieYes Logo