Why did Tesla's stock value drop by 40 USD for just 5 minutes today (Aug 2 3:20pm)?

Clash Royale CLAN TAG#URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
31
down vote
favorite
What caused such a drop in stock value in the span of 10 minutes?

stocks stock-analysis
 |Â
show 3 more comments
up vote
31
down vote
favorite
What caused such a drop in stock value in the span of 10 minutes?

stocks stock-analysis
40
A good confirmation that it's spurious is that it supposedly spiked down to exactly the previous closing price. That's a plausible artifact of a missing data value.
â nanoman
yesterday
What website is this?
â NooBskie
yesterday
1
@NooBskie Google Finance
â zakinster
yesterday
1
It's bad data. TSLA did not drop $40 at 3:30 PM
â Bob Baerker
yesterday
3
I thought Google was a reliable resource ¯_(ãÂÂ)_/¯
â Klik
yesterday
 |Â
show 3 more comments
up vote
31
down vote
favorite
up vote
31
down vote
favorite
What caused such a drop in stock value in the span of 10 minutes?

stocks stock-analysis
What caused such a drop in stock value in the span of 10 minutes?

stocks stock-analysis
asked yesterday
Klik
27724
27724
40
A good confirmation that it's spurious is that it supposedly spiked down to exactly the previous closing price. That's a plausible artifact of a missing data value.
â nanoman
yesterday
What website is this?
â NooBskie
yesterday
1
@NooBskie Google Finance
â zakinster
yesterday
1
It's bad data. TSLA did not drop $40 at 3:30 PM
â Bob Baerker
yesterday
3
I thought Google was a reliable resource ¯_(ãÂÂ)_/¯
â Klik
yesterday
 |Â
show 3 more comments
40
A good confirmation that it's spurious is that it supposedly spiked down to exactly the previous closing price. That's a plausible artifact of a missing data value.
â nanoman
yesterday
What website is this?
â NooBskie
yesterday
1
@NooBskie Google Finance
â zakinster
yesterday
1
It's bad data. TSLA did not drop $40 at 3:30 PM
â Bob Baerker
yesterday
3
I thought Google was a reliable resource ¯_(ãÂÂ)_/¯
â Klik
yesterday
40
40
A good confirmation that it's spurious is that it supposedly spiked down to exactly the previous closing price. That's a plausible artifact of a missing data value.
â nanoman
yesterday
A good confirmation that it's spurious is that it supposedly spiked down to exactly the previous closing price. That's a plausible artifact of a missing data value.
â nanoman
yesterday
What website is this?
â NooBskie
yesterday
What website is this?
â NooBskie
yesterday
1
1
@NooBskie Google Finance
â zakinster
yesterday
@NooBskie Google Finance
â zakinster
yesterday
1
1
It's bad data. TSLA did not drop $40 at 3:30 PM
â Bob Baerker
yesterday
It's bad data. TSLA did not drop $40 at 3:30 PM
â Bob Baerker
yesterday
3
3
I thought Google was a reliable resource ¯_(ãÂÂ)_/¯
â Klik
yesterday
I thought Google was a reliable resource ¯_(ãÂÂ)_/¯
â Klik
yesterday
 |Â
show 3 more comments
2 Answers
2
active
oldest
votes
up vote
69
down vote
Refresh the report. You'll probably see that dip gone. It was likely just a glitch in the reporting data when you happened to run it. Oddities like this happen from time to time. When you see something extreme like this, it's best to check multiple sources and re-run the reports again a bit later.

When I worked at TipRanks I was surprised at how common those data issues were - with ~5000 stocks and 3 data providers there was always some stock showing an incorrect price at some data provider (and to be clear, showing real time stock prices is expensive). I'd wake up from alerts and GOOGL would be $100,000 a share for just 5 minutes. This sort of thing is way too common.
â Benjamin Gruenbaum
10 hours ago
add a comment |Â
up vote
1
down vote
There are only a couple of companies that provide exchange data and there are a ton of resellers. Websites that get data take in data feeds and big web sites connect their API with the feed provider's.
In this case there was probably a trade published at that price. It could have been fixed almost instantly or 5 mins later or an hour later. The exchange would fix it and send the message through its API to the feed of one of the big exchange feed providers.
This for sure happens. Now either the API of the exchange feed provider was not working properly - did not cancel out the trade and refresh - or the API between the exchange feed provider and the website was not working right.
I would really rule out it being an issue with one of the providers as this is a huge company to have a data issue with and would probably filter to hundreds/thousands of websites if it was an issue there.
So the most likely scenario is this website's API does not does not actively look for refresh messages and probably has them on a schedule - some websites just wrap them up at the end of market. Some may do them once an hour and so on. And some that do them at the end of market but get complaints on a stock this popular will force a refresh out of the norm. Just an average day in running financial web apps.
(On a side note as I don't want to take away with how things logistically work. Most errors come in the end of market wrap up. Meaning I am guessing that the 3:30 time was the end of the normal market hours for that exchange. The exchanges usually dump everything all at once - this is because daily highs/lows/volume and key stats are usually a reflection of market hours not after market moves. And during this data dump there is a much much higher chance of wrong messages sent. It is very likely that someone had a bid listed at that price that was never executed but an end of market program executed it as a trade briefly)
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
69
down vote
Refresh the report. You'll probably see that dip gone. It was likely just a glitch in the reporting data when you happened to run it. Oddities like this happen from time to time. When you see something extreme like this, it's best to check multiple sources and re-run the reports again a bit later.

When I worked at TipRanks I was surprised at how common those data issues were - with ~5000 stocks and 3 data providers there was always some stock showing an incorrect price at some data provider (and to be clear, showing real time stock prices is expensive). I'd wake up from alerts and GOOGL would be $100,000 a share for just 5 minutes. This sort of thing is way too common.
â Benjamin Gruenbaum
10 hours ago
add a comment |Â
up vote
69
down vote
Refresh the report. You'll probably see that dip gone. It was likely just a glitch in the reporting data when you happened to run it. Oddities like this happen from time to time. When you see something extreme like this, it's best to check multiple sources and re-run the reports again a bit later.

When I worked at TipRanks I was surprised at how common those data issues were - with ~5000 stocks and 3 data providers there was always some stock showing an incorrect price at some data provider (and to be clear, showing real time stock prices is expensive). I'd wake up from alerts and GOOGL would be $100,000 a share for just 5 minutes. This sort of thing is way too common.
â Benjamin Gruenbaum
10 hours ago
add a comment |Â
up vote
69
down vote
up vote
69
down vote
Refresh the report. You'll probably see that dip gone. It was likely just a glitch in the reporting data when you happened to run it. Oddities like this happen from time to time. When you see something extreme like this, it's best to check multiple sources and re-run the reports again a bit later.

Refresh the report. You'll probably see that dip gone. It was likely just a glitch in the reporting data when you happened to run it. Oddities like this happen from time to time. When you see something extreme like this, it's best to check multiple sources and re-run the reports again a bit later.

answered yesterday
BobbyScon
10.1k32650
10.1k32650
When I worked at TipRanks I was surprised at how common those data issues were - with ~5000 stocks and 3 data providers there was always some stock showing an incorrect price at some data provider (and to be clear, showing real time stock prices is expensive). I'd wake up from alerts and GOOGL would be $100,000 a share for just 5 minutes. This sort of thing is way too common.
â Benjamin Gruenbaum
10 hours ago
add a comment |Â
When I worked at TipRanks I was surprised at how common those data issues were - with ~5000 stocks and 3 data providers there was always some stock showing an incorrect price at some data provider (and to be clear, showing real time stock prices is expensive). I'd wake up from alerts and GOOGL would be $100,000 a share for just 5 minutes. This sort of thing is way too common.
â Benjamin Gruenbaum
10 hours ago
When I worked at TipRanks I was surprised at how common those data issues were - with ~5000 stocks and 3 data providers there was always some stock showing an incorrect price at some data provider (and to be clear, showing real time stock prices is expensive). I'd wake up from alerts and GOOGL would be $100,000 a share for just 5 minutes. This sort of thing is way too common.
â Benjamin Gruenbaum
10 hours ago
When I worked at TipRanks I was surprised at how common those data issues were - with ~5000 stocks and 3 data providers there was always some stock showing an incorrect price at some data provider (and to be clear, showing real time stock prices is expensive). I'd wake up from alerts and GOOGL would be $100,000 a share for just 5 minutes. This sort of thing is way too common.
â Benjamin Gruenbaum
10 hours ago
add a comment |Â
up vote
1
down vote
There are only a couple of companies that provide exchange data and there are a ton of resellers. Websites that get data take in data feeds and big web sites connect their API with the feed provider's.
In this case there was probably a trade published at that price. It could have been fixed almost instantly or 5 mins later or an hour later. The exchange would fix it and send the message through its API to the feed of one of the big exchange feed providers.
This for sure happens. Now either the API of the exchange feed provider was not working properly - did not cancel out the trade and refresh - or the API between the exchange feed provider and the website was not working right.
I would really rule out it being an issue with one of the providers as this is a huge company to have a data issue with and would probably filter to hundreds/thousands of websites if it was an issue there.
So the most likely scenario is this website's API does not does not actively look for refresh messages and probably has them on a schedule - some websites just wrap them up at the end of market. Some may do them once an hour and so on. And some that do them at the end of market but get complaints on a stock this popular will force a refresh out of the norm. Just an average day in running financial web apps.
(On a side note as I don't want to take away with how things logistically work. Most errors come in the end of market wrap up. Meaning I am guessing that the 3:30 time was the end of the normal market hours for that exchange. The exchanges usually dump everything all at once - this is because daily highs/lows/volume and key stats are usually a reflection of market hours not after market moves. And during this data dump there is a much much higher chance of wrong messages sent. It is very likely that someone had a bid listed at that price that was never executed but an end of market program executed it as a trade briefly)
add a comment |Â
up vote
1
down vote
There are only a couple of companies that provide exchange data and there are a ton of resellers. Websites that get data take in data feeds and big web sites connect their API with the feed provider's.
In this case there was probably a trade published at that price. It could have been fixed almost instantly or 5 mins later or an hour later. The exchange would fix it and send the message through its API to the feed of one of the big exchange feed providers.
This for sure happens. Now either the API of the exchange feed provider was not working properly - did not cancel out the trade and refresh - or the API between the exchange feed provider and the website was not working right.
I would really rule out it being an issue with one of the providers as this is a huge company to have a data issue with and would probably filter to hundreds/thousands of websites if it was an issue there.
So the most likely scenario is this website's API does not does not actively look for refresh messages and probably has them on a schedule - some websites just wrap them up at the end of market. Some may do them once an hour and so on. And some that do them at the end of market but get complaints on a stock this popular will force a refresh out of the norm. Just an average day in running financial web apps.
(On a side note as I don't want to take away with how things logistically work. Most errors come in the end of market wrap up. Meaning I am guessing that the 3:30 time was the end of the normal market hours for that exchange. The exchanges usually dump everything all at once - this is because daily highs/lows/volume and key stats are usually a reflection of market hours not after market moves. And during this data dump there is a much much higher chance of wrong messages sent. It is very likely that someone had a bid listed at that price that was never executed but an end of market program executed it as a trade briefly)
add a comment |Â
up vote
1
down vote
up vote
1
down vote
There are only a couple of companies that provide exchange data and there are a ton of resellers. Websites that get data take in data feeds and big web sites connect their API with the feed provider's.
In this case there was probably a trade published at that price. It could have been fixed almost instantly or 5 mins later or an hour later. The exchange would fix it and send the message through its API to the feed of one of the big exchange feed providers.
This for sure happens. Now either the API of the exchange feed provider was not working properly - did not cancel out the trade and refresh - or the API between the exchange feed provider and the website was not working right.
I would really rule out it being an issue with one of the providers as this is a huge company to have a data issue with and would probably filter to hundreds/thousands of websites if it was an issue there.
So the most likely scenario is this website's API does not does not actively look for refresh messages and probably has them on a schedule - some websites just wrap them up at the end of market. Some may do them once an hour and so on. And some that do them at the end of market but get complaints on a stock this popular will force a refresh out of the norm. Just an average day in running financial web apps.
(On a side note as I don't want to take away with how things logistically work. Most errors come in the end of market wrap up. Meaning I am guessing that the 3:30 time was the end of the normal market hours for that exchange. The exchanges usually dump everything all at once - this is because daily highs/lows/volume and key stats are usually a reflection of market hours not after market moves. And during this data dump there is a much much higher chance of wrong messages sent. It is very likely that someone had a bid listed at that price that was never executed but an end of market program executed it as a trade briefly)
There are only a couple of companies that provide exchange data and there are a ton of resellers. Websites that get data take in data feeds and big web sites connect their API with the feed provider's.
In this case there was probably a trade published at that price. It could have been fixed almost instantly or 5 mins later or an hour later. The exchange would fix it and send the message through its API to the feed of one of the big exchange feed providers.
This for sure happens. Now either the API of the exchange feed provider was not working properly - did not cancel out the trade and refresh - or the API between the exchange feed provider and the website was not working right.
I would really rule out it being an issue with one of the providers as this is a huge company to have a data issue with and would probably filter to hundreds/thousands of websites if it was an issue there.
So the most likely scenario is this website's API does not does not actively look for refresh messages and probably has them on a schedule - some websites just wrap them up at the end of market. Some may do them once an hour and so on. And some that do them at the end of market but get complaints on a stock this popular will force a refresh out of the norm. Just an average day in running financial web apps.
(On a side note as I don't want to take away with how things logistically work. Most errors come in the end of market wrap up. Meaning I am guessing that the 3:30 time was the end of the normal market hours for that exchange. The exchanges usually dump everything all at once - this is because daily highs/lows/volume and key stats are usually a reflection of market hours not after market moves. And during this data dump there is a much much higher chance of wrong messages sent. It is very likely that someone had a bid listed at that price that was never executed but an end of market program executed it as a trade briefly)
answered yesterday
blankip
2,097614
2,097614
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmoney.stackexchange.com%2fquestions%2f98207%2fwhy-did-teslas-stock-value-drop-by-40-usd-for-just-5-minutes-today-aug-2-320p%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
40
A good confirmation that it's spurious is that it supposedly spiked down to exactly the previous closing price. That's a plausible artifact of a missing data value.
â nanoman
yesterday
What website is this?
â NooBskie
yesterday
1
@NooBskie Google Finance
â zakinster
yesterday
1
It's bad data. TSLA did not drop $40 at 3:30 PM
â Bob Baerker
yesterday
3
I thought Google was a reliable resource ¯_(ãÂÂ)_/¯
â Klik
yesterday