<?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>iCore Solutions Status - Incident history</title>
    <link>https://status.icoresolutions.com</link>
    <description>iCore Solutions</description>
    <pubDate>Tue, 23 Jun 2026 09:53:54 +0000</pubDate>
    
<item>
  <title>Incident identified</title>
  <description>
    Type: Incident
    Duration: 4 hours and 44 minutes

    
    Jun 23, 09:53:54 GMT+0 - Investigating - We are aware of an issue affecting accessing Nodes in iCCS production environment

Our team is actively investigating the root cause. We will provide an update within \[30 minutes / 1 hour\].

We apologize for any disruption to your operations. Jun 23, 10:25:16 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 23, 10:45:40 GMT+0 - Investigating - We are currently investigating this incident with support from Microsoft. Jun 23, 11:09:19 GMT+0 - Investigating - We are currently investigating this incident with support from Microsoft. Jun 23, 11:38:04 GMT+0 - Investigating - We are currently investigating this incident. We are having a problem with anazure storage account and we are working with an azure technician to identify the issue. Jun 23, 12:14:04 GMT+0 - Investigating - We are investigating the incident. Jun 23, 13:37:54 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 23, 14:38:17 GMT+0 - Resolved - We can confirm that the issue affecting access to the Node Directory has been fully resolved. All iCCS integrations are now operating normally.

We apologize for the inconvenience this incident caused. A follow-up summary will be shared \[within 24 hours / in due time\] for customers who require additional information.

Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 44 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:53:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of an issue affecting accessing Nodes in iCCS production environment

Our team is actively investigating the root cause. We will provide an update within \[30 minutes / 1 hour\].

We apologize for any disruption to your operations..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:25:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:45:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident with support from Microsoft..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:09:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident with support from Microsoft..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:38:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident. We are having a problem with anazure storage account and we are working with an azure technician to identify the issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:14:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are investigating the incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:37:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:38:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We can confirm that the issue affecting access to the Node Directory has been fully resolved. All iCCS integrations are now operating normally.

We apologize for the inconvenience this incident caused. A follow-up summary will be shared \[within 24 hours / in due time\] for customers who require additional information.

Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 23 Jun 2026 09:53:54 +0000</pubDate>
  <link>https://status.icoresolutions.com/incident/cmqqgvxns0s5x2opf889r37ti</link>
  <guid>https://status.icoresolutions.com/incident/cmqqgvxns0s5x2opf889r37ti</guid>
</item>

  </channel>
  </rss>