<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:oiiku.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://oiiku.instatus.com/history.atom"/>
  <title>Oiiku Status - Incident history</title>
  <updated>2026-02-25T21:00:00.000+00:00</updated>
  <author>
    <name>Oiiku</name>
  </author>
  
<entry>
  <id>tag:oiiku.instatus.com,2005:Incident/cmm3792ck0mq9hrimxlm743an</id>
  <published>2026-02-25T21:00:00.000+00:00</published>
  <updated>2026-02-25T21:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/incident/cmm3792ck0mq9hrimxlm743an"/>
  <title>Service outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> Oiiku Webapp, Oiiku Screens, Oiiku Badges, Oiiku Attendees, Oiiku Pages, Oiiku Events, Oiiku Messages, Oiiku Users, Oiiku Placement</p>
    <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  All Oiiku services were down between 22:00 and 22:11 tonight. The problem was caused by a faulty router at our hosting provider..</p>
<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>21:11:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:oiiku.instatus.com,2005:Maintenance/cmkmfcc3t0hzk4liiafr562a9</id>
  <published>2026-02-01T08:00:00.000+00:00</published>
  <updated>2026-02-01T08:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/maintenance/cmkmfcc3t0hzk4liiafr562a9"/>
  <title>Email template editor maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Oiiku Messages</p>
    <p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our email template editor, Stripo, is updating their infrastructure. During this 1-hour maintenance window it won&#039;t be possible to create, modify or save email templates..</p>
<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>08:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:oiiku.instatus.com,2005:Incident/cmkz91ima00214ets0mjt6dtu</id>
  <published>2026-01-28T23:05:00.000+00:00</published>
  <updated>2026-01-28T23:05:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/incident/cmkz91ima00214ets0mjt6dtu"/>
  <title>Service outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 38 minutes</p>
    <p><strong>Affected Components:</strong> Oiiku Webapp, Oiiku Screens, Oiiku Badges, Oiiku Attendees, Oiiku Pages, Oiiku Events, Oiiku Messages, Oiiku Users, Oiiku Placement</p>
    <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>23:05:00</var> GMT+0</small><br /><strong>Identified</strong> -
  All Oiiku services were fully or partially down between 00:05 and 00:43 tonight. The problem was caused by a faulty network component at our hosting provider..</p>
<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>23:43:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:oiiku.instatus.com,2005:Maintenance/cmifzshus00qci9uoso1jasog</id>
  <published>2025-11-27T05:00:00.000+00:00</published>
  <updated>2025-11-27T05:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/maintenance/cmifzshus00qci9uoso1jasog"/>
  <title>Server maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 15 minutes</p>
    <p><strong>Affected Components:</strong> Oiiku Webapp, Oiiku Screens, Oiiku Users, Oiiku Badges, Oiiku Attendees, Oiiku Placement, Oiiku Pages, Oiiku Events, Oiiku Messages</p>
    <p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance to update our servers..</p>
<p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>05:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>06:14:55</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:oiiku.instatus.com,2005:Maintenance/cmi8vc82r01wa7kkxvy7whizd</id>
  <published>2025-11-24T04:00:00.000+00:00</published>
  <updated>2025-11-24T04:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/maintenance/cmi8vc82r01wa7kkxvy7whizd"/>
  <title>Server maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 9 minutes</p>
    <p><strong>Affected Components:</strong> Oiiku Screens, Oiiku Users, Oiiku Badges, Oiiku Attendees, Oiiku Placement, Oiiku Pages, Oiiku Events, Oiiku Messages, Oiiku Webapp</p>
    <p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;re doing work to ensure our servers continue to function flawlessly..</p>
<p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>05:09:04</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:oiiku.instatus.com,2005:Incident/cmi8usxy00b3onyitgsrqkkcg</id>
  <published>2025-11-20T17:13:00.000+00:00</published>
  <updated>2025-11-20T17:42:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/incident/cmi8usxy00b3onyitgsrqkkcg"/>
  <title>Oiiku Pages and Placement outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> Oiiku Placement, Oiiku Pages</p>
    <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>17:42:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  All systems are now operational..</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>17:13:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Due to a network problem at our hosting provider, the database that is serving the Pages and Placement modules went offline for a period of about 30 minutes. Pages and Placement were unavailable in that interval. They both came back online at 18:42 (CET)..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:oiiku.instatus.com,2005:Incident/cm9b7xjob004u12rnwy4tcg5f</id>
  <published>2025-04-10T10:31:40.365+00:00</published>
  <updated>2025-04-10T10:31:40.365+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/incident/cm9b7xjob004u12rnwy4tcg5f"/>
  <title>Issue with views in Attendees module</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Oiiku Attendees</p>
    <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>10:31:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  This morning, we discovered that a change to our server configuration last night caused user views to behave incorrectly. Because of this, you may have noticed one of the following:

• Views for your events were missing

• You saw views from other users in your organization

**When this happened:**

The issue affected views between **23:15 CEST last night** and **11:10 CEST today**, when it was fixed.

If you exported views during that time, the spreadsheet might include the wrong attendees and columns.

**A few important things to know:**

• Your saved views were _not_ lost — they should now appear correctly again

• If you created new views during the affected period, you’ll need to recreate them

• No attendee data was compromised

If things still don’t look right, just reach out and we’ll help you get it sorted.

We’re really sorry for the trouble this caused. We’ve put new checks in place to make sure it doesn’t happen again..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:oiiku.instatus.com,2005:Incident/clxoiyuc83532b1lqctkpuqjw</id>
  <published>2024-06-19T06:35:00.000+00:00</published>
  <updated>2024-06-19T06:35:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://oiiku.instatus.com/incident/clxoiyuc83532b1lqctkpuqjw"/>
  <title>Webapp taken down due to suspected brute-force attack</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> Oiiku Webapp</p>
    <p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>06:35:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>06:38:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have verified that this is a brute-force attack. An automated attack by someone to test millions random app links, to find valid ones. We took webapp down to stop the attack, and protect personal data. We are implementing measures to block the attacker and will take webapp back online again as soon as possible..</p>
<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>08:35:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Measures to stop attack have been implemented. Does not seem like the attack has been successful. Webapp is back online. We will monitor closely and check all system logs to get the full picture..</p>
<p><small>Jun <var data-var='date'> 19</var>, <var data-var='time'>15:23:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  No further attacks since we took webapp back online. No valid app links was generated in the attack. No personal data was exposed. Will send email with &quot;post mortem&quot; to clients later tonight..</p>

        ]]>
  </content>
</entry>

</feed>