<?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>Telleroo status Status - Incident history</title>
    <link>https://status.telleroo.com</link>
    <description>Telleroo status</description>
    <pubDate>Fri, 24 Apr 2026 05:45:19 +0000</pubDate>
    
<item>
  <title>Payments showing at awaiting funds with enough balance in the account. </title>
  <description>
    Type: Incident
    Duration: 23 minutes

    Affected Components: GBP, FX
    Apr 24, 05:45:19 GMT+0 - Investigating - We are currently investigating this incident. Apr 24, 05:58:38 GMT+0 - Identified - Our team have identified the issue affecting a small subset of payments and working on a fix.  Apr 24, 06:02:10 GMT+0 - Monitoring - Our team have resolved the issue and payments are now being sent.  Apr 24, 06:08:42 GMT+0 - Resolved - This incident has been resolved, all payments have been sent and will be in the recipients bank account within the 2 hour faster payment timescle if not already.  Apr 24, 09:45:14 GMT+0 - Postmortem - **Technical Update**: Processing Delay Resolved  
We recently identified and corrected a technical synchronisation issue that caused a temporary delay for a small percentage of payment transactions.  
**Issue Overview** 
The delay was linked to a recent system optimisation intended to enhance transaction security and prevent processing errors. While the update performed its primary security function, it created an unintended bottleneck in one of our automated workflows. This resulted in some transactions failing to advance to the final processing stage automatically.  
**Resolution &amp; Current Status** 
Our engineering team has implemented a permanent fix to restore full automation across all processing pathways.

* **Immediate Mitigation:** During the resolution window, we utilised a background process to ensure all affected transactions were identified and successfully processed.
* **System Correction:** A logic update has been deployed to ensure that our enhanced security protocols and automated processing workflows function in perfect alignment.
* **Current Status:** All systems are operating normally, and the backlog of affected payments has been cleared. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:45: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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:58:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our team have identified the issue affecting a small subset of payments and working on a fix. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:02:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Our team have resolved the issue and payments are now being sent. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:08:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved, all payments have been sent and will be in the recipients bank account within the 2 hour faster payment timescle if not already. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:45:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  **Technical Update**: Processing Delay Resolved  
We recently identified and corrected a technical synchronisation issue that caused a temporary delay for a small percentage of payment transactions.  
**Issue Overview** 
The delay was linked to a recent system optimisation intended to enhance transaction security and prevent processing errors. While the update performed its primary security function, it created an unintended bottleneck in one of our automated workflows. This resulted in some transactions failing to advance to the final processing stage automatically.  
**Resolution &amp; Current Status** 
Our engineering team has implemented a permanent fix to restore full automation across all processing pathways.

* **Immediate Mitigation:** During the resolution window, we utilised a background process to ensure all affected transactions were identified and successfully processed.
* **System Correction:** A logic update has been deployed to ensure that our enhanced security protocols and automated processing workflows function in perfect alignment.
* **Current Status:** All systems are operating normally, and the backlog of affected payments has been cleared..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 24 Apr 2026 05:45:19 +0000</pubDate>
  <link>https://status.telleroo.com/incident/cmochl4qv001nf04utufy4cu0</link>
  <guid>https://status.telleroo.com/incident/cmochl4qv001nf04utufy4cu0</guid>
</item>

<item>
  <title>FX Payment Delays</title>
  <description>
    Type: Incident
    Duration: 2 hours and 44 minutes

    Affected Components: FX
    Mar 19, 12:38:59 GMT+0 - Resolved - This incident has been resolved. Mar 19, 09:55:03 GMT+0 - Investigating - We are currently investigating this incident. Mar 19, 10:48:33 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:38:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:55:03&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;Mar &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:48:33&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;
]]>
  </content:encoded>
  <pubDate>Thu, 19 Mar 2026 09:55:03 +0000</pubDate>
  <link>https://status.telleroo.com/incident/cmmxanmpq000jlxot7tvowztd</link>
  <guid>https://status.telleroo.com/incident/cmmxanmpq000jlxot7tvowztd</guid>
</item>

<item>
  <title>Issues with MXN Transfers </title>
  <description>
    Type: Incident
    Duration: 5 days, 23 hours and 50 minutes

    Affected Components: FX
    Mar 9, 11:02:21 GMT+0 - Resolved - This incident has been resolved. Mar 3, 11:12:17 GMT+0 - Investigating - We are currently investigating an issue affecting MXN transfers only, no other currency affected 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 23 hours and 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:02:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:12:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an issue affecting MXN transfers only, no other currency affected.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 3 Mar 2026 11:12:17 +0000</pubDate>
  <link>https://status.telleroo.com/incident/cmmaidbqr0aumtjjs1htpz70x</link>
  <guid>https://status.telleroo.com/incident/cmmaidbqr0aumtjjs1htpz70x</guid>
</item>

<item>
  <title>Delay to payments settling</title>
  <description>
    Type: Incident
    Duration: 3 hours and 36 minutes

    Affected Components: GBP, FX, , 
Payments →
    Feb 27, 09:48:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 27, 10:38:31 GMT+0 - Identified - Our banking partner has identified the issue on their side and they are working to resolve it. Feb 27, 10:50:16 GMT+0 - Identified - New payments are processing as normal, working to clear payments not sent that were due to be processed between 09:00 and 10:30, please do not attempt to reprocess any payments. Feb 27, 12:09:15 GMT+0 - Identified - Credits into Telleroo during the impacted period have now been reflected within the Telleroo system.  Feb 27, 12:52:08 GMT+0 - Monitoring - Held payments are now processing and will move to paid.  Feb 27, 13:24:04 GMT+0 - Resolved - This incident has been resolved and held payments for the technical issue at our partner bank have been sent.  
  
We do fully apologise for any inconvenience.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:48: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;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:38:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our banking partner has identified the issue on their side and they are working to resolve it..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:50:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  New payments are processing as normal, working to clear payments not sent that were due to be processed between 09:00 and 10:30, please do not attempt to reprocess any payments..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:09:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Credits into Telleroo during the impacted period have now been reflected within the Telleroo system. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:52:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Held payments are now processing and will move to paid. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:24:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved and held payments for the technical issue at our partner bank have been sent.  
  
We do fully apologise for any inconvenience. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 27 Feb 2026 09:48:00 +0000</pubDate>
  <link>https://status.telleroo.com/incident/cmm4q5inv00rdl6b9lmz48izr</link>
  <guid>https://status.telleroo.com/incident/cmm4q5inv00rdl6b9lmz48izr</guid>
</item>

<item>
  <title>A few customers have reported being unable to approve payments</title>
  <description>
    Type: Incident
    Duration: 57 minutes

    Affected Components: GBP, FX, , 
Payments →
    Feb 2, 17:11:49 GMT+0 - Investigating - We are currently investigating this incident. Feb 2, 18:08:48 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 57 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:11:49&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;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:08:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Feb 2026 17:11:49 +0000</pubDate>
  <link>https://status.telleroo.com/incident/cml5ffzjn03pua9s24kgawe94</link>
  <guid>https://status.telleroo.com/incident/cml5ffzjn03pua9s24kgawe94</guid>
</item>

<item>
  <title>Slowness in payment processing</title>
  <description>
    Type: Incident
    Duration: 2 hours and 10 minutes

    Affected Components: GBP, FX
    Feb 2, 14:03:45 GMT+0 - Investigating - We are currently investigating this incident. Feb 2, 14:41:17 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 2, 15:38:18 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 2, 16:14:10 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:03:45&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;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:41:17&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;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:38:18&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;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:14:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Feb 2026 14:03:45 +0000</pubDate>
  <link>https://status.telleroo.com/incident/cml58q4a7022el1wo7usnap8i</link>
  <guid>https://status.telleroo.com/incident/cml58q4a7022el1wo7usnap8i</guid>
</item>

<item>
  <title>Delay in payments moving to paid</title>
  <description>
    Type: Incident
    Duration: 42 minutes

    Affected Components: GBP, FX, , 
Payments →
    Jan 26, 16:27:20 GMT+0 - Investigating - We are currently investigating this incident. Jan 26, 16:33:01 GMT+0 - Monitoring - Our team identified an issue with delay in webhooks from our partners causing the issue, payments are now being moved to paid by our team and they continue to monitor. Jan 26, 17:05:03 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 26, 17:08:52 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:27:20&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;Jan &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:33:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Our team identified an issue with delay in webhooks from our partners causing the issue, payments are now being moved to paid by our team and they continue to monitor..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:05:03&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;Jan &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:08:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 26 Jan 2026 16:27:20 +0000</pubDate>
  <link>https://status.telleroo.com/incident/cmkvdrtg00149t684gwzsct00</link>
  <guid>https://status.telleroo.com/incident/cmkvdrtg00149t684gwzsct00</guid>
</item>

  </channel>
  </rss>