Deprecated: Function get_magic_quotes_gpc() is deprecated in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 99
Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 619
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 832
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839
Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 839 tag:status.rubygems.org,2005:/historyRubyGems.org Status - Incident History2025-10-20T17:41:05ZRubyGems.orgtag:status.rubygems.org,2005:Incident/267604952025-10-17T02:15:14Z2025-10-17T02:15:14ZGem pushes with attestation failing<p><small>Oct <var data-var='date'>17</var>, <var data-var='time'>02:15</var> UTC</small><br><strong>Update</strong> - We're continuing to work with the sigstore team to help resolve users being unable to gem pushes with attestations. For the time being, we recommend users update their workflows to retry gem pushes without attestations.</p><p><small>Oct <var data-var='date'>15</var>, <var data-var='time'>23:04</var> UTC</small><br><strong>Update</strong> - We have implemented a fix for gem pushes that use attestations on rubygems.org. However, gems that rely on the release-gem GitHub Action (https://github.com/rubygems/release-gem) to deploy to rubygems.org will still experience errors. The release-gem action will automatically retry pushing to rubygems.org without attestations, which continue to function as expected.<br /><br />We are closely monitoring the situation and collaborating with the Sigstore team to resolve this issue.</p><p><small>Oct <var data-var='date'>15</var>, <var data-var='time'>06:56</var> UTC</small><br><strong>Identified</strong> - Gem pushes utilising the attestation feature are failing and will respond with an application error. We've identified the issue and are currently working to push a fix.</p>tag:status.rubygems.org,2005:Incident/172227822023-05-12T01:01:20Z2023-05-12T01:01:20ZGoogle Safe Browsing flag as malware<p><small>May <var data-var='date'>12</var>, <var data-var='time'>01:01</var> UTC</small><br><strong>Resolved</strong> - Success! Google Safe Browsing has removed the malware flag from rubygems.org. Special thanks are owed to everyone who connected us to the Chrome and Safe Browsing teams, and the team members who assisted in clearing this up.</p><p><small>May <var data-var='date'>11</var>, <var data-var='time'>22:01</var> UTC</small><br><strong>Update</strong> - We have heard that our appeal has successfully been escalated within the Google Safe Browsing team, and they are working to resolve things.</p><p><small>May <var data-var='date'>11</var>, <var data-var='time'>21:45</var> UTC</small><br><strong>Identified</strong> - Google Safe Browsing has flagged the entire rubygems.org domain as malware, impacting all users of the Chrome, Safari, and Firefox browser.<br /><br />The underlying issue appears to be an incorrect malware flag applied to all versions of a gem from the metasploit family. In our investigation we’ve identified that the same library is also available from GitHub and many Linux and BSD distro packages. We continue investigating, sharing information and working with Google to resolve this as soon as possible.<br /><br />For the time being, there are no other issues: the website can be accessed as normal if you bypass the warning. Gem downloads and pushes continue working as normal.</p>tag:status.rubygems.org,2005:Incident/159770022023-01-30T20:00:23Z2023-01-30T20:00:26ZUpdates to search infrastructure<p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>20:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>19:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>18:41</var> UTC</small><br><strong>Scheduled</strong> - We will be upgrading our search cluster, and search results from the web interface may briefly become slow or fail to return.</p>tag:status.rubygems.org,2005:Incident/75340802021-07-18T14:30:32Z2021-07-18T14:30:32ZScheduled maintenance<p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>14:30</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>13:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>18:12</var> UTC</small><br><strong>Scheduled</strong> - We will be performing maintenance on our Kubernetes cluster. It won't cause any downtime on any of our services.</p>tag:status.rubygems.org,2005:Incident/71957772021-06-08T11:29:49Z2021-06-08T11:29:49ZElevated Errors<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>11:29</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>11:03</var> UTC</small><br><strong>Monitoring</strong> - Our CDN provider has applied a fix and over the last few minutes we saw traffic levels and errors return to normal.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>10:46</var> UTC</small><br><strong>Identified</strong> - Our CDN partner has identified the issue and a fix is being implemented.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>10:12</var> UTC</small><br><strong>Update</strong> - The elevated 503 and 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/vpk0ssybt3bj.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level of errors and are currently looking into the issue.</p>tag:status.rubygems.org,2005:Incident/71323862021-06-01T17:40:29Z2021-06-01T17:40:29ZScheduled maintenance<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>17:40</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>17:30</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>May <var data-var='date'>31</var>, <var data-var='time'>18:32</var> UTC</small><br><strong>Scheduled</strong> - We will be performing maintenance on our Elasticsearch cluster. You may experience a brief interruption on our search endpoints. We expect this to only be 5-10 minutes at the most. Gem downloads and dependency API won't be impacted.</p>tag:status.rubygems.org,2005:Incident/63450852021-02-21T13:44:30Z2021-02-21T13:44:30ZDatabase Maintenance<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>13:44</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance of our database has been completed.</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>17:52</var> UTC</small><br><strong>Scheduled</strong> - We will be performing database maintenance. You may experience a brief interruption in our services, which should not last longer than 5 minutes. Gem downloads will continue to work, and some API endpoints will continue to return cached data.</p>tag:status.rubygems.org,2005:Incident/60062392021-01-12T16:55:08Z2021-01-12T16:55:09ZUnexpected Errors<p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>16:55</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>16:28</var> UTC</small><br><strong>Monitoring</strong> - Fastly has implemented a fix and we are monitoring the results.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>16:14</var> UTC</small><br><strong>Identified</strong> - The elevated 502 errors seem to be because of Fastly's ongoing incident. We are following along at https://status.fastly.com/incidents/1rbr326kjsmt.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>16:02</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level of errors and are currently looking into the issue.</p>tag:status.rubygems.org,2005:Incident/46442462020-07-17T22:01:05Z2020-07-17T22:01:06ZElevated DNS Errors<p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>22:01</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>21:53</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>21:42</var> UTC</small><br><strong>Monitoring</strong> - DNS seems to be resolving again. We continue to monitor the situation.</p><p><small>Jul <var data-var='date'>17</var>, <var data-var='time'>21:20</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level of DNS errors and are currently looking into the issue.</p>tag:status.rubygems.org,2005:Incident/39603282020-04-25T10:16:51Z2020-04-25T10:16:52ZUsers unable to access RubyGems.org<p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>10:16</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>10:03</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>10:03</var> UTC</small><br><strong>Investigating</strong> - We're currently investigating users being unable to access rubygems.org</p>tag:status.rubygems.org,2005:Incident/38226182020-04-03T21:33:39Z2020-04-03T21:33:39ZDNS resolution errors for some users<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>21:33</var> UTC</small><br><strong>Resolved</strong> - DNS resolution should be working for all users now.</p><p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>16:15</var> UTC</small><br><strong>Identified</strong> - We are currently investigating DNS resolution errors for some users.</p>tag:status.rubygems.org,2005:Incident/36062522020-02-24T11:03:48Z2020-02-24T13:31:00ZUnexpected Problem<p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>11:03</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>10:53</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Feb <var data-var='date'>24</var>, <var data-var='time'>10:38</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.rubygems.org,2005:Incident/22642952019-03-17T03:49:38Z2019-03-17T03:49:38ZDatabase Maintenance<p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>03:49</var> UTC</small><br><strong>Completed</strong> - The database maintenance was completed with 19 minutes of downtime. Thanks for your patience!</p><p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>03:16</var> UTC</small><br><strong>Verifying</strong> - Verification is currently underway for the maintenance items.</p><p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>02:45</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is beginning now. We expect about 30 minutes of downtime.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>13:32</var> UTC</small><br><strong>Scheduled</strong> - We will be performing database maintenance later today. We expect downtime of some services for a short period during this time. Gem downloads will continue to work, and some API endpoints will continue to return cached data. We will provide more updates immediately before we begin.</p>tag:status.rubygems.org,2005:Incident/21821192019-01-31T11:15:34Z2019-01-31T13:22:03ZUnexpected Problem<p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>11:15</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>10:55</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>10:42</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level errors and are currently looking into the issue.</p>tag:status.rubygems.org,2005:Incident/21457342019-01-13T23:44:07Z2019-01-13T23:44:07ZElevated Errors<p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>23:44</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>16:53</var> UTC</small><br><strong>Monitoring</strong> - Over the last 20 minutes we experienced an elevated level of errors. We are currently monitoring the issue.</p>tag:status.rubygems.org,2005:Incident/21453622019-01-13T09:36:54Z2019-01-13T09:36:54ZUnexpected Problem<p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>09:36</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>09:33</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>09:05</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an unexpected problem and are currently looking into the issue.</p>tag:status.rubygems.org,2005:Incident/21241022019-01-01T14:26:57Z2019-01-01T14:26:57ZProblems installing gems<p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>14:26</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved. All gems should be included in the versions API again.</p><p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>14:19</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jan <var data-var='date'> 1</var>, <var data-var='time'>14:02</var> UTC</small><br><strong>Identified</strong> - We have received reports of some gems not being able to be installed. We have identified the issue and we are working on resolving it. Gems published before 2015-08-23 may be unlisted on the versions API.</p>tag:status.rubygems.org,2005:Incident/15462792017-12-26T09:56:23Z2017-12-26T09:56:23ZUnexpected Problem<p><small>Dec <var data-var='date'>26</var>, <var data-var='time'>09:56</var> UTC</small><br><strong>Resolved</strong> - The site has been stable since 19:15 UTC.</p><p><small>Dec <var data-var='date'>25</var>, <var data-var='time'>22:25</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p><p><small>Dec <var data-var='date'>25</var>, <var data-var='time'>20:21</var> UTC</small><br><strong>Monitoring</strong> - All services should be working now. We will continue to monitor.</p><p><small>Dec <var data-var='date'>25</var>, <var data-var='time'>20:08</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level of errors and are currently looking into the issue.</p>tag:status.rubygems.org,2005:Incident/12217982017-05-02T16:07:25Z2017-05-02T16:07:25ZUnexpected problem<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>16:07</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'> 2</var>, <var data-var='time'>16:05</var> UTC</small><br><strong>Update</strong> - We receive reports that a major ISP had a complete outage between the United States and Europe for about 20 minutes at 14:45 UTC.</p><p><small>May <var data-var='date'> 2</var>, <var data-var='time'>15:14</var> UTC</small><br><strong>Monitoring</strong> - Our upstream provider has implemented a fix and we are monitoring the results. We are also seeing reports of general internet issues in Europe. We will post more information as we get it.</p><p><small>May <var data-var='date'> 2</var>, <var data-var='time'>14:58</var> UTC</small><br><strong>Investigating</strong> - We are aware of reports that services are unavailable in some regions. We're looking into it now!</p>tag:status.rubygems.org,2005:Incident/12227052017-05-02T12:00:00Z2017-05-02T12:00:00ZProblems accessing RubyGems.org using TLS 1.1<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>Resolved</strong> - We received reports of legacy software being unable to access RubyGems.org. Specifically anyone using TLS 1.1. This is common on older operating systems like Ubuntu Precise 12.04.
<br />
<br />We quickly realized that our CDN provider had disabled TLS 1.1 today due to a previously announced deprecation of TLS 1.1. Unfortunately we hadn't taken steps to avoid this action today. Once we realized what had happened we migrated back to a configuration that allowed TLS 1.1.
<br />
<br />I'm sorry if this impacted you today. Everything should be working again now. If you are still having issues please submit a help ticket.
<br />
<br />The migration today is a short term change, and in the future we will be permanently disabling support for TLS 1.1. We will announce these dates.</p>tag:status.rubygems.org,2005:Incident/9364832016-10-03T22:22:17Z2016-10-03T22:22:18ZGem index delays<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>22:22</var> UTC</small><br><strong>Resolved</strong> - All gems appear to be installing successfully.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>19:42</var> UTC</small><br><strong>Monitoring</strong> - All gems should be indexed now. We are monitoring to make sure new gems are added in a timely manor.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>19:34</var> UTC</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>19:23</var> UTC</small><br><strong>Investigating</strong> - We're aware that new gems published may not be added to the new gem index in a timely manor. Our team is investigating.
<br />
<br />Running 'bundle install --full-index', as well as 'gem install' are unaffected by this delay.</p>tag:status.rubygems.org,2005:Incident/7646662016-09-12T13:05:04Z2016-09-12T13:05:04ZDNS Problems<p><small>Sep <var data-var='date'>12</var>, <var data-var='time'>13:05</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>12</var>, <var data-var='time'>03:36</var> UTC</small><br><strong>Monitoring</strong> - We are continuing to monitor the DNS propagation.</p><p><small>Sep <var data-var='date'>12</var>, <var data-var='time'>03:29</var> UTC</small><br><strong>Identified</strong> - We have identified and fixed the problem. Service will be restored as soon as DNS propagates.</p><p><small>Sep <var data-var='date'>12</var>, <var data-var='time'>03:17</var> UTC</small><br><strong>Investigating</strong> - We are receiving reports of DNS problems. We are investigating.</p>tag:status.rubygems.org,2005:Incident/7600032016-09-07T01:58:43Z2016-09-07T01:58:43ZElevated Errors<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>01:58</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>20:36</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level of errors and are currently looking into the issue.</p>tag:status.rubygems.org,2005:Incident/7601422016-09-07T01:58:31Z2016-09-07T01:58:31ZEmergency Maintenance<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>01:58</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>01:24</var> UTC</small><br><strong>Verifying</strong> - Verification is currently underway for the maintenance items.</p><p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>01:13</var> UTC</small><br><strong>In progress</strong> - We have started our database maintenance.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>23:19</var> UTC</small><br><strong>Scheduled</strong> - We will be performing emergency database maintenance. All website and api services will be down during this period. Gem downloads and the new index will continue to work. We will post more updates as we have them.</p>tag:status.rubygems.org,2005:Incident/5436642016-06-27T22:03:04Z2016-06-27T22:03:04ZElevated response times<p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>22:03</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>19:44</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>18:47</var> UTC</small><br><strong>Investigating</strong> - We're experiencing elevated response times and are currently looking into the issue.</p>