Istoricul incidentelor Medium

We are investigating an issue where stats pages are missing data or are slow to update. Please bear with us.

We have identified the issue, and the data is being processed to the stats pages.

This issue is resolved. If you still have issues, please contact us at help.medium.com

``` We are aware of an issue affecting some users who recently upgraded their membership through the iOS App Store. These users may not see their updated membership status reflected accurately across the platform. Existing memberships are not affected. Our team is actively investigating the root cause and we will provide updates as more information becomes available. ```

We have identified the root cause and a fix has been applied. New membership upgrades made through the iOS App Store should now be processed and reflected accurately. We are still working on resolving membership status for users who were affected during the incident window.

We have identified the root cause and a fix has been applied. New membership upgrades made through the iOS App Store are now processed and reflected accurately. Users who were affected during the incident window or are noticing discrepancies between their App Store subscription status and Medium membership status can use the "Restore purchase" option in the Medium iOS app settings to go back to normal. Please contact Medium support if you are still experiencing issues.

We are investigating production issues.

Problem has been identified and fixed.

We’re aware that some users in India are experiencing difficulties accessing Medium on the website and in our mobile apps. This does **not appear to be caused by a change on Medium’s side**, and our engineering team is actively investigating the underlying issue with connectivity from certain networks. **Temporary workaround:** If you’re currently unable to access Medium, switching your device’s DNS settings from your ISP’s default DNS to a public DNS resolver may help. For example: • **Cloudflare DNS:** 1.1.1.1 and 1.0.0.1 • **Google Public DNS:** 8.8.8.8 and 8.8.4.4 This change is optional and reversible, and it may restore access while we continue our investigation. We’re sorry for the inconvenience and will share updates as soon as we have more information.

Airtel resolved the DNS issue on their side.

We have identified elevated 500 errors in accessing parts of [medium.com](http://medium.com "medium.com"). We have identified the issue, and are working as quickly as possible to address the issue.

This morning, we identified some underlying databases to be overloaded. We have since added capacity, and expect the cause of these elevated errors to be remediated. We are continuing to monitor the situation to validate our findings, and ensure there are no outstanding causes. Please contact Medium User Support with any questions or concerns.

All services remain operational. The remediations we have implemented are keeping the platform stable, but we are continuing to monitor to ensure that we have solved the underlying problem. For any issues, please [submit a request in our Help Center](https://help.medium.com/hc/en-us?source=home-------------------------------------------- "submit a request in our Help Center").

We identified some upstream database throttling that resulted in the 500 errors observed by some users. We have since addressed the issue across multiple surfaces.

We are aware of an issue causing some users to see a "Something went wrong" error when accessing the site. Our team is currently investigating the cause and working to resolve it as quickly as possible. We will provide updates as more information becomes available.

We have implemented a fix and are starting to see the site recover. We will continue to monitor the situation closely to ensure stability and will provide further updates if necessary.

This incident has been resolved. Thank you for your patience as we addressed this issue.

We are aware of issues accessing the Medium website and mobile apps. We will update this status when more information is available.

Cloudflare released a fix at 09:12 UTC which seems to have resolved the issue for the Medium website and mobile apps. We’re now monitoring.

The issue is now resolved.

A small number of users is reporting that they are unable to log into Medium from their corporate networks. We are actively investigating the issue and will provide an update as quickly as possible.

We now better understand that this is **_not_** a widespread issue. A small subset of user traffic is being characterized as automated, and the patterns match that of traffic that may be sitting behind a specific type of network proxy. We are now investigating the best way to allow this type of legitimate traffic through our firewalls, and will update again when more information is available.

This incident is now resolved.

We have identified an issue where some users have incorrectly received an e-mail indicating that they have incomplete payout settings and that earnings could not be sent. If your Partner Program Dashboard shows that your payout settings are complete and that "You are eligible to receive payouts from Medium.", please disregard the e-mail. We have identified the cause for the e-mail targeting some users incorrectly, and we are working to remediate this issue immediately. Users will not see any immediate indicators of this correction, as it is purely in our backend at this time. If you have any questions, please contact our user support services at [https://help.medium.com/hc/en-us/requests/new](https://help.medium.com/hc/en-us/requests/new "https://help.medium.com/hc/en-us/requests/new")

Changes have been deployed to prevent further erroneous e-mails surrounding Partner Program payout settings. If you receive an e-mail and believe it is in error, please contact our User Support Services at: [https://help.medium.com/hc/en-us/requests/new](https://help.medium.com/hc/en-us/requests/new "https://help.medium.com/hc/en-us/requests/new")

The underlying issue that caused these e-mails to be sent has been addressed. We do not expect any further erroneous e-mails to be sent. Please contact User Support if any other issues are obseved.

Medium's CDN provider: Cloudflare, experienced an outage from 11:48 to 14:42 UTC. This resulted in some users being unable to access [Medium.com](http://medium.com/), among other websites like Spotify, Facebook, and X. According to [Cloudflare's status page](https://www.cloudflarestatus.com/), the issue was resolved as of 14:42 UTC. You should now be able to resume reading and writing on Medium.

We are hearing reports of issues accessing Medium.com from India. **This is not something Medium has done. **This is happening at or above the Internet Service Provider (ISP) level. Traffic from a number of ISP's in India is pointing to the wrong IP address for [medium.com](http://medium.com). We are attempting to contact the direct department at each ISP.  **We urge you to contact your ISP directly, report this problem, and push them for a resolution.** • **Specifically escalate this matter to the NOC / DNS team** • **Tell them that multiple ISPs, including yours, are pointing to the wrong IP address. ** • **Going to [medium.com](http://medium.com) should point to a Cloudflare IP address** • **If it points to anything else, that is wrong. It is most likely pointing an IP address on Amazon’s network** • **Ask them to clear or correct their DNS cache for medium.com.**

If you are having issues connecting to Medium from India, we recommend changing the DNS address on your devices to replace your ISP’s DNS (like Airtel, Jio, or Vi) with a **public resolver** such as: • **Cloudflare:** 1.1.1.1 and 1.0.0.1 • **Google Public DNS:** 8.8.8.8 and 8.8.4.4

Based on our data, it looks like access is being restored to certain ISPs. If you’re still having difficulties, please continue to reach out to your ISP in addition to updating your DNS resolvers on your devices.

The incident with access in India is now resolved.

Medium is experiencing an outage due to an outage involving AWS services. We are working with AWS to resolve the issue as quickly as possible.

We are seeing some signs of recovery. We are still actively monitoring the situation.

AWS is once again reporting an outage. We are working with AWS to resolve the issue as quickly as possible.

There continues to be a disruption because of the ongoing AWS outage. We are closely monitoring the situation and will continue to update as we work to identify remediation.

AWS service recovery is underway. We are beginning to see some stability and have begin to bring Medium's systems back online. We continue to see elevated 500 errors as a result of lingering outage-related disruption. We are continuing to mitigate as much as possible, and will update again as we have more information available.

Most Medium services have recovered after the major provider outage. Stats are not yet 100% recovered and will take additional time to catch up. We will provide an update around that tomorrow (21-October) as we continue to monitor the situation closely.

Stats have finished processing after the major provider outage, and all Medium services and functionality have been fully restored.

We are aware that there may be a large delay when performing certain actions within the publication. For example, there may be a delay between the time the story is accepted and when it is displayed on the homepage, when the publication layout is updated, or when the submitted story statuses are updated. The team is working to improve this now. Please subscribe to this status to receive updates.

There continue to be delays when performing certain actions within publications. There are multiple, parallel efforts underway to address the issue. Some fixes have already shipped, so we are hopeful the experience will improve soon. More updates to follow as we ship more fixes directly tied to this issue.

We appreciate your patience. We have identified the missing core data dependencies that connect stories with publications, and are working to fix those now. Please bear with us.

Numerous improvements have been shipped this week. While we still see some degraded performance and abnormal behavior with publication pages, we are beginning to see improved backend performance. Some additional fixes are still underway, and we will continue to provide updates as further improvements are made to the components powering publications. In the meantime, please continue to report abnormalities as they are encountered.

**Update - 27-October** Some additional fixes have taken effect as of today. We are seeing improvements in new posts showing up in Publications. This behavior should be visibly improved. Please continue reporting any new occurrences of this behavior, as we are still working to improve the experience in Publications. Some other problematic behaviors remain and are still being investigated. These include (but are not limited to) posts appearing in Publications that should no longer do so and layout updates not being immediately reflected. We will continue to provide updates as additional improvements deploy.

We are seeing improvements from the changes we have deployed, and can confirm reduced frequency in the issues related to posts being shared in publications. We are continuing to improve the reliability of this product surface, and will continue to provide updates as we validate the impact of our changes as they relate to specific behaviors. We appreciate the patience as we continue to investigate and apply fixes as quickly as possible. If you continue to experience any issues with your publication, please submit a request at [help.medium.com](http://help.medium.com "help.medium.com")

We have shipped a large number of improvements that have largely decreased the number of posts failing to appear in Publications. In addition, work has been done to stabilize other surfaces relating to Publications and their layouts. We are confident that a large majority of the behaviors observed have been stabilized, but acknowledge that some users may still experience abnormalities. If you experience undesired behavior in your publication, please contact us at [help.medium.com](http://help.medium.com "help.medium.com") so that we can better understand the nature of the problem, and address it as soon as possible.

Additional improvements have been shipped to stabilize the behaviors observed by editors in Publications, including: • Posts failing to appear • Posts mistakenly appearing where they should not • Layout changes not reflected in a timely manner We are confident that layout issues are now resolved, and that a large majority of post-related issues are as well. Some users may still experience abnormalities. We are actively working on changes to address the issue as quickly as possible. While we deploy additional fixes, we expect some post ordering may change within publications. If you experience any undesired behavior within your publication, please contact us at [help.medium.com](http://help.medium.com "help.medium.com") so that we can ensure your specific issues are taken into account and addressed swiftly.

All fixes related to anomalous Publications behaviors have been deployed. Specifically, these changes have addressed behaviors including: • Posts failing to appear • Posts mistakenly appearing where they should not • Layout changes not reflected in a timely manner At this time, we no long expect these behaviors to persist. If any abnormalities are observed with relation to Publications, please open a new issue via [help.medium.com](http://help.medium.com "help.medium.com").

We are investigating an issue that has caused stats processing to be delayed, and stats to show as zero for October 8.

Stats for Oct 8 have been processed, and we are monitoring processing as it continues to run.

Stats processing has been restored.

## Resolved An internal dependency update broke real-time reconciliation for external traffic routing. This **only** impacted Custom Domains on our legacy infrastructure (CDv1). This issue has been resolved.