tag:status.url2png.com,2005:/historyURL2PNG Status - Incident History2024-03-29T01:23:06-04:00URL2PNGtag:status.url2png.com,2005:Incident/186808332023-10-03T18:02:45-04:002023-10-03T18:02:45-04:00production traffic is impaired<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>18:02</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>15:58</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>15:07</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/184603922023-09-10T10:30:00-04:002023-09-10T15:21:37-04:00truncated viewport<p><small>Sep <var data-var='date'>10</var>, <var data-var='time'>10:30</var> EDT</small><br><strong>Resolved</strong> - Starting at 10:30AM EDT, api requests with a defined viewport may have resulted in an image 4px shorter than expected. Image width was not impacted. As of 2:40PM EDT, this issue has been resolved.</p>tag:status.url2png.com,2005:Incident/159345942023-01-25T14:06:42-05:002023-01-25T14:06:42-05:00production traffic impaired<p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>14:06</var> EST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>14:00</var> EST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>13:44</var> EST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>13:26</var> EST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/102918392022-06-14T21:39:15-04:002022-06-14T21:39:15-04:00Production traffic partially impaired on API - Capture<p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>21:39</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>21:32</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>20:49</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/81316992021-10-01T14:13:04-04:002021-10-01T14:13:04-04:00Production traffic impaired<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>14:13</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>13:35</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p>tag:status.url2png.com,2005:Incident/78094862021-08-20T17:47:51-04:002021-08-20T17:47:51-04:00Production traffic impaired<p><small>Aug <var data-var='date'>20</var>, <var data-var='time'>17:47</var> EDT</small><br><strong>Resolved</strong> - Starting at 21:00 UTC fresh captures started experiencing increased latency, with some request timing out and resulting in an error response. The majority of requests during this window did capture the desired page, despite the initial error response. At 21:15 UTC all traffic and error levels have returned to normal.</p><p><small>Aug <var data-var='date'>20</var>, <var data-var='time'>17:10</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Aug <var data-var='date'>20</var>, <var data-var='time'>17:00</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/72302282021-06-12T03:57:53-04:002021-06-12T03:57:53-04:00Production traffic impaired<p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>03:57</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>03:01</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>02:48</var> EDT</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>01:12</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/71967682021-06-08T09:48:38-04:002021-06-08T09:48:38-04:00Upstream Global CDN Outage<p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>09:48</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>07:30</var> EDT</small><br><strong>Monitoring</strong> - Fastly, our upstream CDN provider, suffered a service disruption starting at Jun 08, 2021 - 09:58 UTC. At Jun 08, 2021 - 10:57 UTC a fix was deployed on Fastly's systems and they are monitoring the situation presently.<br /><br />At this time all systems are operation on our end, but we are reviewing/monitoring traffic patterns during the return of global traffic and playing catch up with delayed requests now being processed and populating our outer most cache layer. <br /><br />Incident Report for Fastly: ( Global CDN Disruption - https://status.fastly.com/incidents/vpk0ssybt3bj )</p>tag:status.url2png.com,2005:Incident/69366232021-05-06T15:51:21-04:002021-05-06T15:51:21-04:00Impaired production traffic<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>15:51</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>May <var data-var='date'> 6</var>, <var data-var='time'>14:38</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>May <var data-var='date'> 6</var>, <var data-var='time'>11:52</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/67267432021-04-11T12:45:31-04:002021-04-11T12:45:31-04:00limited production traffic impaired<p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>12:45</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>10:05</var> EDT</small><br><strong>Monitoring</strong> - The cold cache layer behind our CDN became impaired, resulting in several short windows of high latency responses and a small number of error responses within those windows. We have repaired the cold cache layer infrastructure, and it is actively rebuilding and returning to normal operations. All requests are processing normally at this time, but the system will remain in monitoring until 12pm EST.</p><p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>09:07</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/55981502020-11-18T19:18:16-05:002020-11-18T19:18:16-05:00Production traffic impaired<p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>19:18</var> EST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>18:40</var> EST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.<br /><br />(Fresh captures impaired from 23:37- 23:40 UTC. Cached results were not impacted.)</p>tag:status.url2png.com,2005:Incident/49940982020-09-01T11:17:20-04:002020-09-01T11:17:20-04:00Increased latency on fresh captures (cached assets not impacted)<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>11:17</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>11:08</var> EDT</small><br><strong>Monitoring</strong> - Capture times returning to normal. Related incident: https://status.fastly.com/incidents/8bk8y5q158pk</p><p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>10:58</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/49742282020-08-30T14:53:46-04:002020-08-30T14:53:46-04:00Upstream network/ip transit issues impacting traffic in some regions<p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>14:53</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>09:27</var> EDT</small><br><strong>Update</strong> - At this time there is a global scale outage across a number of providers. Capturing against the internet is expected to be error prone until global routing is corrected/stabilized.</p><p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>07:34</var> EDT</small><br><strong>Monitoring</strong> - https://status.fastly.com/incidents/p1lwmmv2j2gq</p>tag:status.url2png.com,2005:Incident/47582502020-08-01T12:30:00-04:002020-08-01T14:13:54-04:00url2png.com site/dashboard outage<p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>12:30</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p>tag:status.url2png.com,2005:Incident/43515372020-06-12T15:09:27-04:002020-06-12T15:09:27-04:00CDN communication issues for www.url2png.com<p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>15:09</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>15:05</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>14:56</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/38228062020-04-02T13:48:11-04:002020-04-02T13:48:11-04:00Production traffic impaired<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>13:48</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>12:57</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>12:56</var> EDT</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>12:55</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/37747212020-03-24T11:10:22-04:002020-03-24T12:01:25-04:00production traffic impaired<p><small>Mar <var data-var='date'>24</var>, <var data-var='time'>11:10</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p>tag:status.url2png.com,2005:Incident/37684482020-03-23T11:04:34-04:002020-03-24T11:15:54-04:00disruption to production traffic<p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>11:04</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>10:14</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>09:56</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/34629352020-01-23T17:59:33-05:002020-01-23T17:59:33-05:00upstream connectivity issues (NYC)<p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>17:59</var> EST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>12:40</var> EST</small><br><strong>Monitoring</strong> - Digital Ocean has reported connectivity issues in their NYC1 region: https://status.digitalocean.com/incidents/lvyhmpwhvdt4<br /><br />We did briefly observe an impact to instances in that region (and sites hosted from the region). At this time the impact appears limited. This incident will be kept in monitoring until the parent incident is fully resolved.</p>tag:status.url2png.com,2005:Incident/31307552019-10-22T18:38:04-04:002019-10-22T18:38:04-04:00elevated rate of 500s in production<p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>18:38</var> EDT</small><br><strong>Resolved</strong> - Making as resolved at this time. We will post an additional update once public statements are available from AWS on their ongoing DNS challenges today.<br />- https://news.ycombinator.com/item?id=21327980</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>15:53</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>15:45</var> EDT</small><br><strong>Update</strong> - The upstream dns/network issue has gotten considerably worse. At this time we have deployed a fleet wide work around. Error rates should continue to drop with this in place. We are actively monitoring the situation and will update as we deploy any additional resolutions.</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>15:40</var> EDT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>12:28</var> EDT</small><br><strong>Update</strong> - Related upstream event: https://status.digitalocean.com/incidents/1z3kmlvz69v6</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>08:40</var> EDT</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Oct <var data-var='date'>22</var>, <var data-var='time'>08:21</var> EDT</small><br><strong>Investigating</strong> - Some request types are experiencing an elevated rate of 500s. Initial evidence points to transient upstream connectivity issues, but we are investigating as current status updates from AWS/DigitalOcean do not account for our regions at this time.</p>tag:status.url2png.com,2005:Incident/29418872019-08-31T13:41:52-04:002019-08-31T13:41:52-04:00api.url2png.com routing outage<p><small>Aug <var data-var='date'>31</var>, <var data-var='time'>13:41</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>31</var>, <var data-var='time'>09:14</var> EDT</small><br><strong>Monitoring</strong> - Around 12:44 UTC we experienced a routing outage for api.url2png.com. At 12:58 UTC we cut over to alternative routing and service has been restored. We will continue to monitor the situation.</p>tag:status.url2png.com,2005:Incident/24839232019-06-02T20:23:45-04:002019-06-02T20:23:45-04:00beta api end point non-responsive<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>20:23</var> EDT</small><br><strong>Resolved</strong> - Full captures resumed as of Jun 02 23:25:08 UTC. Google declared their outage to have ended as of 2019-06-02 11:45 (UTC).</p><p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>18:11</var> EDT</small><br><strong>Update</strong> - If you have important capture traffic running on the beta api endpoint, we recommend you shift to the production api endpoint heading forward. Keep in mind, capturing assets still impacted by this outage will likely result in errors and/or abnormal asset capture.</p><p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>15:46</var> EDT</small><br><strong>Identified</strong> - This outage is related to a broader outage of upstream providers. See https://status.cloud.google.com/incident/compute/19003 however the impact is broader than just url2png, sites and services being served by GCP seem unavailable for many customers.</p><p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>15:14</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/22435152019-03-06T06:38:00-05:002019-03-06T06:38:00-05:00elevated rate of 504s on fresh captures<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>06:38</var> EST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>06:00</var> EST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>04:21</var> EST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>03:10</var> EST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.url2png.com,2005:Incident/21755792019-01-30T07:31:14-05:002019-01-30T07:33:00-05:00slow capture times being experienced on beta.url2png.com<p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>07:31</var> EST</small><br><strong>Resolved</strong> - This incident was resolved somewhat prior, but beta continued to experience infrequent network related issues. At this time we are seeing more stable capture traffic patterns. Customers are advised to move production traffic away from the beta endpoint and reach out to support about any blocking issues related to rendering or beta-specific features.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>21:47</var> EST</small><br><strong>Monitoring</strong> - We are still seeing some infrequent networking issues, but capture times have returned to normal.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>16:57</var> EST</small><br><strong>Investigating</strong> - Our upstream provider is experiencing compute/network outages in regions important to this service end point (beta). We have launched additional capacity in other unaffected regions, but are still investigating and seeing network related impacts across regions.</p>tag:status.url2png.com,2005:Incident/20392492018-11-15T14:08:40-05:002018-11-15T14:08:40-05:00api.url2png.com was impaired, rejecting new capture requests<p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>14:08</var> EST</small><br><strong>Resolved</strong> - api.url2png.com rejected new capture requests from approximate 17.50:00 to 17.59:00 UTC. All jobs are processing as normal since that time. Assets already in the CDN were not impacted during this time.</p>