<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:archive.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://archive.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://archive.instatus.com/history.atom"/>
  <title>Archive Status - Incident history</title>
  <updated>2025-11-12T04:00:00.000+00:00</updated>
  <author>
    <name>Archive</name>
  </author>
  
<entry>
  <id>tag:archive.instatus.com,2005:Incident/cmhvtugys00fboo9726ct9zwn</id>
  <published>2025-11-12T04:00:00.000+00:00</published>
  <updated>2025-11-12T04:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://archive.instatus.com/incident/cmhvtugys00fboo9726ct9zwn"/>
  <title>Archive Services Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> Archive App, API</p>
    <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently experiencing a service disruption affecting all services running on our domain. The outage began at 10:15 PM EST on November 12, 2025..</p>
<p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>12:55:23</var> GMT+0</small><br /><strong>Resolved</strong> -
  On **November 11 at approximately 10:15 PM EST**, our primary domain experienced a **temporary configuration issue** that caused interruptions across Archive services.  
Our team worked quickly to resolve the issue and monitor DNS propagation worldwide. While recovery timelines for this type of issue typically take **24–48 hours**, we&#039;re happy to confirm that **service was restored much faster and all systems are now fully operational**.  
We&#039;re also implementing additional safeguards to prevent this from happening again.  
If you have any questions, please get in touch with our support team at [support@archive.com](mailto:support@archive.com)..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:archive.instatus.com,2005:Incident/cmddh228w0049tnphtgsefg0p</id>
  <published>2025-07-21T19:01:39.808+00:00</published>
  <updated>2025-07-23T19:48:59.086+00:00</updated>
  <link rel="alternate" type="text/html" href="https://archive.instatus.com/incident/cmddh228w0049tnphtgsefg0p"/>
  <title>Delays with content delivery from Instagram</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 15 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> Instagram Integration</p>
    <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>19:48:59</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our processing queues are nearly fully normalized. We expect to confirm complete resolution shortly and will share a final update as soon as it’s fully resolved..</p>
<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>19:01:39</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We’re currently experiencing delays with content delivery from Instagram. Your content is being saved correctly, but it may take longer than usual to appear in your workspace. Our engineering team is actively working to resolve the issue. .</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>14:00:04</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Currently, the delay only affects Reels and Feed Posts, while Instagram stories should appear in your workspace immediately.

We are continuously working on this and will keep you informed..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>10:58:20</var> GMT+0</small><br /><strong>Resolved</strong> -
  We&#039;ve successfully resolved the processing issues that were affecting Instagram content. Your Reels and Feed posts are now being captured and delivered as expected. Everything&#039;s working smoothly again and content is happily flowing through. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:archive.instatus.com,2005:Maintenance/cli096hzi578795ouoarys5u5yg</id>
  <published>2023-05-24T07:00:00.000+00:00</published>
  <updated>2023-05-24T07:20:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://archive.instatus.com/maintenance/cli096hzi578795ouoarys5u5yg"/>
  <title>Scheduled Brief System Pause on May 24</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    
    <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>07:20:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Just a quick note to let you know that we&#039;re making our system even better. We&#039;re performing an upgrade tomorrow at 3 a.m. Miami time. There might be a small pause of 15-20 minutes in our services during this time. Thank you for your understanding and patience..</p>

        ]]>
  </content>
</entry>

</feed>