<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Archive Status - Incident history</title>
    <link>https://archive.instatus.com</link>
    <description>Archive</description>
    <pubDate>Fri, 28 Aug 2026 16:30:00 +0000</pubDate>
    
<item>
  <title>We&#039;re aware some users are unable to load the Archive site and are actively investigating.</title>
  <description>
    Type: Incident
    Duration: 4 days, 20 hours and 28 minutes

    Affected Components: Archive App
    Aug 28, 16:30:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 28, 22:39:19 GMT+0 - Identified - We’ve identified that some US internet providers are incorrectly blocking [app.archive.com](http://app.archive.com). While we work with them to resolve this, affected users can access Archive at &lt;https://app.archive.ai&gt; using their existing login and workspace. Sep 1, 13:09:22 GMT+0 - Identified - Access has been restored on some affected networks, but [app.archive.com](http://app.archive.com) may remain unavailable for some users while we continue working with third-party providers. If you’re affected, please use &lt;https://app.archive.ai&gt; with your existing login and workspace. Sep 2, 12:58:18 GMT+0 - Resolved - This incident has been resolved. Access to [app.archive.com](http://app.archive.com) has been restored across the affected networks, and customers can access Archive normally. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 20 hours and 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:39:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We’ve identified that some US internet providers are incorrectly blocking [app.archive.com](http://app.archive.com). While we work with them to resolve this, affected users can access Archive at &lt;https://app.archive.ai&gt; using their existing login and workspace..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:09:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Access has been restored on some affected networks, but [app.archive.com](http://app.archive.com) may remain unavailable for some users while we continue working with third-party providers. If you’re affected, please use &lt;https://app.archive.ai&gt; with your existing login and workspace..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:58:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. Access to [app.archive.com](http://app.archive.com) has been restored across the affected networks, and customers can access Archive normally..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 28 Aug 2026 16:30:00 +0000</pubDate>
  <link>https://archive.instatus.com/incident/cmtdcp3ed02891bqrk1soj2fp</link>
  <guid>https://archive.instatus.com/incident/cmtdcp3ed02891bqrk1soj2fp</guid>
</item>

<item>
  <title>Archive Services Outage</title>
  <description>
    Type: Incident
    Duration: 8 hours and 55 minutes

    Affected Components: Archive App, API
    Nov 12, 04:00:00 GMT+0 - Identified - 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. Nov 12, 12:55:23 GMT+0 - Resolved - 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). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:55:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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)..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 12 Nov 2025 04:00:00 +0000</pubDate>
  <link>https://archive.instatus.com/incident/cmhvtugys00fboo9726ct9zwn</link>
  <guid>https://archive.instatus.com/incident/cmhvtugys00fboo9726ct9zwn</guid>
</item>

<item>
  <title>Delays with content delivery from Instagram</title>
  <description>
    Type: Incident
    Duration: 6 days, 15 hours and 57 minutes

    Affected Components: Instagram Integration
    Jul 23, 19:48:59 GMT+0 - Monitoring - 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. Jul 21, 19:01:39 GMT+0 - Monitoring - 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.  Jul 22, 14:00:04 GMT+0 - Monitoring - 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. Jul 28, 10:58:20 GMT+0 - Resolved - 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.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 15 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:48:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:01:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:58:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 21 Jul 2025 19:01:39 +0000</pubDate>
  <link>https://archive.instatus.com/incident/cmddh228w0049tnphtgsefg0p</link>
  <guid>https://archive.instatus.com/incident/cmddh228w0049tnphtgsefg0p</guid>
</item>

<item>
  <title>Scheduled Brief System Pause on May 24</title>
  <description>
    Type: Maintenance
    Duration: 20 minutes

    
    May 24, 07:20:00 GMT+0 - Completed - Maintenance has completed successfully May 24, 07:00:01 GMT+0 - Identified - Maintenance is now in progress May 24, 07:00:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 24 May 2023 07:00:00 +0000</pubDate>
  <link>https://archive.instatus.com/maintenance/cli096hzi578795ouoarys5u5yg</link>
  <guid>https://archive.instatus.com/maintenance/cli096hzi578795ouoarys5u5yg</guid>
</item>

  </channel>
  </rss>