<?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>1RPC Status - Incident history</title>
    <link>https://status.1rpc.io</link>
    <description>1RPC</description>
    <pubDate>Mon, 4 Mar 2024 15:00:00 +0000</pubDate>
    
<item>
  <title>1RPC partial outage</title>
  <description>
    Type: Incident
    Duration: 4 hours

    Affected Components: 1RPC Taiko Katla, 1RPC Acala, 1RPC Gnosis Mainnet, 1RPC Avalanche C-Chain, 1RPC OKT Chain Mainnet, 1RPC Polygon zkEVM Beta, 1RPC Astar, 1RPC Moonbeam, 1RPC Aurora, 1RPC Scroll Sepolia Testnet, 1RPC Mode Testnet, 1RPC Cronos Mainnet, 1RPC Base Mainnet, 1RPC AltLayer, 1RPC Avalanche P-Chain, 1RPC Manta, 1RPC Linea, 1RPC Mantle Mainnet, 1RPC Automata Testnet, 1RPC Sui, 1RPC Fantom Opera, 1RPC BNB Mainnet, 1RPC Osmosis, 1RPC Klaytn, 1RPC Oasis Sapphire, 1RPC Injective, 1RPC Kusama, 1RPC Scroll Sepolia Testnet, 1RPC Optimism, 1RPC Aptos, 1RPC X Layer Testnet, 1RPC Telos EVM, 1RPC zkSync, 1RPC Polkadot, 1RPC Boba, 1RPC Mode Mainnet, 1RPC Ethereum Mainnet, 1RPC Oasis Emerald, 1RPC Bitcoin, 1RPC Core Blockchain, 1RPC Secret, 1RPC Near Mainnet, 1RPC Harmony, 1RPC Scroll Mainnet, 1RPC Avalanche X-Chain, 1RPC Celo, 1RPC Polygon Mainnet, 1RPC StarkNet, 1RPC Holesky Testnet, 1RPC opBNB Mainnet, 1RPC Axelar, 1RPC Avail Testnet, 1RPC Arbitrum One Mainnet, 1RPC SEI
    Mar 4, 19:00:00 GMT+0 - Resolved - This incident has been resolved. Mar 4, 18:04:30 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 4, 15:15:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 4, 15:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>18:04:30</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>15:15:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 4 Mar 2024 15:00:00 +0000</pubDate>
  <link>https://status.1rpc.io/incident/cltd43i0q2598b5ofl1pvrr00</link>
  <guid>https://status.1rpc.io/incident/cltd43i0q2598b5ofl1pvrr00</guid>
</item>

<item>
  <title>1RPC partial outage</title>
  <description>
    Type: Incident
    Duration: 5 hours and 40 minutes

    Affected Components: 1RPC Manta, 1RPC Linea, 1RPC Mantle Mainnet, 1RPC Automata Testnet, 1RPC Sui, 1RPC Fantom Opera, 1RPC Acala, 1RPC Gnosis Mainnet, 1RPC Avalanche C-Chain, 1RPC BNB Mainnet, 1RPC Osmosis, 1RPC Klaytn, 1RPC Oasis Sapphire, 1RPC OKT Chain Mainnet, 1RPC Polygon zkEVM Beta, 1RPC Injective, 1RPC Astar, 1RPC Kusama, 1RPC Scroll Sepolia Testnet, 1RPC Optimism, 1RPC Moonbeam, 1RPC Aptos, 1RPC Aurora, 1RPC X Layer Testnet, 1RPC Scroll Sepolia Testnet, 1RPC Telos EVM, 1RPC zkSync, 1RPC Polkadot, 1RPC Boba, 1RPC Mode Mainnet, 1RPC Mode Testnet, 1RPC Cronos Mainnet, 1RPC Ethereum Mainnet, 1RPC Oasis Emerald, 1RPC Base Mainnet, 1RPC SEI, 1RPC Bitcoin, 1RPC Core Blockchain, 1RPC AltLayer, 1RPC Secret, 1RPC Avalanche P-Chain, 1RPC Near Mainnet, 1RPC Harmony, 1RPC Scroll Mainnet, 1RPC Avalanche X-Chain, 1RPC Celo, 1RPC Polygon Mainnet, 1RPC Taiko Katla, 1RPC StarkNet, 1RPC Holesky Testnet, 1RPC opBNB Mainnet, 1RPC Axelar, 1RPC Avail Testnet, 1RPC Arbitrum One Mainnet
    Feb 29, 15:20:00 GMT+0 - Resolved - This incident has been resolved. Feb 29, 14:30:00 GMT+0 - Monitoring - We have applied a fix and monitoring the status. Feb 29, 14:00:00 GMT+0 - Identified - We located a network issue inside the cloud provider cluster and working on a fix. Feb 29, 09:40:00 GMT+0 - Investigating - Based on the monitoring system, we figured out there is a partial outage issue in 1RPC North Europe cluster. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Feb <var data-var='date'> 29</var>, <var data-var='time'>15:20:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 29</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have applied a fix and monitoring the status..</p>
<p><small>Feb <var data-var='date'> 29</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We located a network issue inside the cloud provider cluster and working on a fix..</p>
<p><small>Feb <var data-var='date'> 29</var>, <var data-var='time'>09:40:00</var> GMT+0</small><br><strong>Investigating</strong> -
  Based on the monitoring system, we figured out there is a partial outage issue in 1RPC North Europe cluster..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 29 Feb 2024 09:40:00 +0000</pubDate>
  <link>https://status.1rpc.io/incident/clt7c4w3d57526b1or57qpbt9m</link>
  <guid>https://status.1rpc.io/incident/clt7c4w3d57526b1or57qpbt9m</guid>
</item>

<item>
  <title>1RPC Manta: Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 13 hours

    Affected Components: 1RPC Manta
    Jan 18, 22:00:00 GMT+0 - Resolved - This incident has been resolved. Jan 18, 18:00:00 GMT+0 - Monitoring - The RPC performance is good now and we are currently monitoring the result. Jan 18, 09:00:00 GMT+0 - Identified - We monitored the Manta Network experienced an RPC flood at around 9AM UTC and it&#039;s also confirmed by their team, the chain is running fine, blocks are producing while the RPC performance is degraded, the accessibility is back online soon. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  The RPC performance is good now and we are currently monitoring the result..</p>
<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We monitored the Manta Network experienced an RPC flood at around 9AM UTC and it&#039;s also confirmed by their team, the chain is running fine, blocks are producing while the RPC performance is degraded, the accessibility is back online soon..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 18 Jan 2024 09:00:00 +0000</pubDate>
  <link>https://status.1rpc.io/incident/clrj1nl1s12140e9ojum18y4sc</link>
  <guid>https://status.1rpc.io/incident/clrj1nl1s12140e9ojum18y4sc</guid>
</item>

<item>
  <title>1RPC Injective: Partial Outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 51 minutes

    Affected Components: 1RPC Injective
    Dec 21, 15:56:37 GMT+0 - Resolved - This incident has been resolved. Dec 21, 15:05:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 21, 14:05:38 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 21, 14:05:38 GMT+0 - Investigating - We are currently investigating this incident since the official endpoint is getting partial outage. Find more details at https://status.injective.network/statuspage/status.injective.network/1850212 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 51 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>15:56:37</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>15:05:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>14:05:38</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>14:05:38</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident since the official endpoint is getting partial outage. Find more details at https://status.injective.network/statuspage/status.injective.network/1850212.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 21 Dec 2023 14:05:38 +0000</pubDate>
  <link>https://status.1rpc.io/incident/clqf9z9rk128656bfn4ovz21wlx</link>
  <guid>https://status.1rpc.io/incident/clqf9z9rk128656bfn4ovz21wlx</guid>
</item>

<item>
  <title>1RPC Polkadot: Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 10 hours and 45 minutes

    Affected Components: 1RPC Polkadot
    Dec 21, 13:45:00 GMT+0 - Resolved - This incident has been resolved. Dec 21, 13:00:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 21, 10:48:29 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 21, 03:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>13:45:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>10:48:29</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Dec <var data-var='date'> 21</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 21 Dec 2023 03:00:00 +0000</pubDate>
  <link>https://status.1rpc.io/incident/clqf1tyqt316266i6oki51go4yh</link>
  <guid>https://status.1rpc.io/incident/clqf1tyqt316266i6oki51go4yh</guid>
</item>

<item>
  <title>Arbitrum Mainnet API outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 22 minutes

    Affected Components: 1RPC Arbitrum One Mainnet
    Dec 15, 18:22:15 GMT+0 - Resolved - This incident has been resolved. Dec 15, 18:00:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 15, 17:10:00 GMT+0 - Identified - We have identified the ongoing issue as a network-related issue. For further details and ongoing updates, please refer to https://status.arbitrum.io/ Dec 15, 17:00:00 GMT+0 - Investigating - We are aware of an outage of some of our Arbitrum Mainnet API endpoints, and the latest block is out-of-date. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>18:22:15</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>17:10:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the ongoing issue as a network-related issue. For further details and ongoing updates, please refer to https://status.arbitrum.io/.</p>
<p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware of an outage of some of our Arbitrum Mainnet API endpoints, and the latest block is out-of-date..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 15 Dec 2023 17:00:00 +0000</pubDate>
  <link>https://status.1rpc.io/incident/clq6xj1sp4395bdohtj6zvo9g</link>
  <guid>https://status.1rpc.io/incident/clq6xj1sp4395bdohtj6zvo9g</guid>
</item>

<item>
  <title>Degraded performance for Arbitrum Mainnet API</title>
  <description>
    Type: Incident
    Duration: 1 hour and 5 minutes

    Affected Components: 1RPC Arbitrum One Mainnet
    Mar 23, 14:25:00 GMT+0 - Resolved - This incident has been resolved. Mar 23, 13:50:00 GMT+0 - Monitoring - We are currently monitoring the result. Mar 23, 13:46:00 GMT+0 - Identified - We are switching to other healthy RPC providers. Mar 23, 13:20:00 GMT+0 - Investigating - We have observed degraded performance on some Arbitrum Mainnet API endpoints and their RPC providers. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>14:25:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>13:50:00</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>13:46:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are switching to other healthy RPC providers..</p>
<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>13:20:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We have observed degraded performance on some Arbitrum Mainnet API endpoints and their RPC providers..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 23 Mar 2023 13:20:00 +0000</pubDate>
  <link>https://status.1rpc.io/incident/clfl81wse332535i9n1alupzzx9</link>
  <guid>https://status.1rpc.io/incident/clfl81wse332535i9n1alupzzx9</guid>
</item>

  </channel>
  </rss>