Is Seeking Alpha Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Due to issues at the upstream service provider, the purchase of new subscriptions is temporary unavailable. We are actively monitoring the issue and will update as soon as the status changes.

This incident has been resolved.

We limited the outage to symbol pages only

A scheduled financial data migration caused global website slowness to a halt

Due to our cloud provider (AWS) connectivity issues, our website was down for 35 minutes. All operations were restored by 11:00 ET.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue is related to partial downtime of our Subscription Management service (Zuora). In the meanwhile, to prevent confusion and inconsistencies we redirected all checkout pages to a temporary error page.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

We are continuing to monitor the situation

We experiencing a partial outage as a result of performance issues on our CDN provider - Fastly. The Fastly team is investigating the issue and we'll update here as soon as new information will come up. https://status.fastly.com/

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Users experience random connection errors from various places in the world. The issue happens on our CDN (Fastly) level: https://status.fastly.com/incidents/1rbr326kjsmt Fastly team is investigating the issue. We'll update here as soon as we'll have new information.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

The database service has been restored, we are monitoring the situation. Some specific data points might be outdated or unavailable for some additional time.

The failed Database service is still down. AWS is working on resolving it. In the meantime, we limited the outage to only symbol pages that are heavily dependent on that database.

One of our main Amazon managed databases is down, we are working with AWS support to fix it ASAP.

RTA's, Newsletters, and other emails are delayed until the service is restored.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We isolated the issue to article pages on mobile and now working on fixing it.

We are continuing to investigate this issue.

We are currently investigating this issue.

We found and resolved the issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

The sending of email alerts and newsletters going forward has been restored.

We temporarily switched transactional emails (registration, personal notifications, etc.) to an alternative provider. Newsletters and Article publishing alerts are still not being sent.

We identified an issue with our email provider and actively working on resolving it.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The server issues have been resolved and the site should now be functioning normally.

We are having sporadic server issues. We are currently investigating. In the meantime, parts of the site may not work properly.

The website was partially down for about 5 minutes and then auto-recovered. We are investigating the cause to try and prevent future incidents like this. Functionality should now be fully restored.

We are currently investigating an issue with our portfolio and other personalized pages. Users may be seeing 500 errors on these pages. We will update once we have identified the issue.

All issues are now resolved.

A fix has been implemented and we are monitoring the results.

We have identified the issue and already implemented a partial fix. The site should be functioning normally except for Marketplace chat which is still down at the moment.

We are currently experiencing server issues. Many parts of the website are impacted. We are investigating and will update as soon as possible.

This incident has been resolved.

We are continuing to investigate this issue.

Our website is currently down. We are working to resolve the issue as fast as possible. Apologies for the inconvenience.

This incident has been resolved.

Our hosting is experiencing problems and are aware of the problem. We're awaiting further updates from them.

We are currently investigating this issue.

The market data issue is now resolved. Apologies for the inconvenience.

Our Market Data provider is currently experiencing an outage. We don't have an ETA yet on a fix, but will monitor closely and update.

This incident has been resolved.

Problem has been solved.

Our market data provider is currently experiencing an outage. This is causing price quotes to not function on our website and mobile apps. We will update when the issue is resolved.

The site performance issues are now resolved. Apologies for any inconvenience.

The site is currently experiencing slowness due to server issues. Some users may also see occasional 500 errors. We have identified the issue and a fix is in progress.

Chat is now functioning. You may need to refresh the page to reload the chat. Apologies for the outage

Marketplace Chat is now down across all services. We have identified the issue and are working to fix. Will update soon.

This is now fixed. OTC data should now be updating normally.

Our data provider is experiencing issues with updating OTC markets data. This is resulting in OTC prices not loading on our desktop site and mobile apps. We are working with them to resolve the issue and will update as soon as it's resolved.

This incident has been resolved.

An upstream provider has confirmed a database networking issue. We are in touch with them and will update further.

We're aware that some features may be performing slower than usual, due to a database issue. We're actively investigating and will update accordingly.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We see that some users may be affected by a server glitch and are working in real-time to rectify it.

This incident has been resolved.

We are aware of an issue and are actively working to resolve it.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

Server connection error continues hitting the CMS servers.

This incident has been resolved.

We identified internal connection error between servers and in the process of fixing it.

This incident has been resolved.

AWS have identified the issue and are actively working on a fix.

There is an outage of AWS S3 services in us-east-1 region. This does not affect our services directly, but may affect some of our partners, hence some users may notice disruption in some parts of SA.

The bug in the code started to affect other areas of the site as well, however the fix has been uploaded and all areas of the site are fully operational.

We are aware of an issue accessing the portfolio page, our developers have identified the bug and are in the process of uploading a fix.

This incident has been resolved.

We are aware that the market data unit in the top right of our homepage is blank. Engineers are working to rectify the issue.

We have been notified by our DNS provider that the incident has been resolved.

Even though it is out of our control, we want our valued users to understand that we are aware that we have been affected by these attacks which started earlier today and continue now. We are in "good company" - other sufferers include New York Times, Heroku, Spotify, Reddit, GitHub, and PagerDuty. Our DNS and CDN partners are working to mitigate the ill effects. Anybody wishing to find out more technical details, search for DNS DDOS in Google News. We'll update this incident report when the attack is over.

Statistics up to date, we'll continue to monitor closely.

We're please to say statistics are now being brought up to date. We'll update further when loading is complete - ETA few hours.

Update: The disk space increase is still in progress and our Plan B failed due to low-level database / SSL renegotiation issues. This has been a crossing over of *three* nasty occurrences. We are leveraging all possible support from our partners, and we are treating this with highest urgency. Statistics are being recorded, and will be published as soon as our database is ready to accept them. Normal browsing of our website is unaffected.

We are upgrading the statistics database disks, and will report back when the upgrade is complete. Counting in the background is still operational. We are also investigating why we weren't pro-actively alerted in this case.

The issue has been resolved. :)

We are aware of connectivity issues and are working to resolve them. ETA for fix - within five minutes, probably less.

The issue has been identified and resolved.

We are aware of issues affecting site performance, and are actively working to resolve them. We'll update on resolution.

This incident has been resolved.

We've identified backend infrastructure failure. Our engineers are deploying a fix.

A fix has been deployed.

Our DB Admin found the malfunctioning code and implementing a solution.

Our monitoring systems notified us about database service disruption. Users may experience partial content on several site components.

This incident has been resolved.

We have rectified the issue.

We are seeing some server instability and we are working in real-time to fix the issue.

This incident has been resolved.

We continue to see intermittent service interruptions, and are working with our hosting company to resolve them.

Issue resolved.

We have identified the issue and things are settling down now. We continue to monitor.

Users may experience intermittent issues. We are investigating and will report back.

We've finished reverting the problematic code, and full service is restored.

Deploying some non-performant code has caused slow performance. We are reverting this at present and will update.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

All services back to normal. Sorry for any disturbance.

We believe the issue is resolved and are now monitoring.

We are having issues with our Redis databases. Some strange behaviour may occur on the site. We are on top of this and will update accordingly.

The issue is fixed, all services are operational.

We are dealing with server issues which may affect performance for some users. We'll update when the issue is resolved.

All systems have been back to full performance for a number of hours, closing incident.

Due to emergency database maintenance, some users may notice disruption to services for the next hour or so. We are on it and will notify when the activity completes.