Lexer Outage History
Lexer is up right nowLexer had 9 outages in the last 2 years totaling 317h 16m of downtime — averaging 0.4 incidents per month.
There were 9 Lexer outages since February 17, 2025 totaling 317h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
Track metric and Activation processing delay
Affected: Hub
Timeline · 5 updates
- investigating Feb 13, 2026, 12:46 AM UTC
We are currently investigating this issue.
- identified Feb 13, 2026, 01:16 AM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 13, 2026, 01:27 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 13, 2026, 02:31 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 13, 2026, 04:28 AM UTC
This incident has been resolved.
Activation performance degraded
Affected: Hub
Timeline · 4 updates
- investigating Jan 09, 2026, 06:11 AM UTC
We're investigating an issue causing activation's to be pending for longer than usual.
- identified Jan 09, 2026, 06:23 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 09, 2026, 06:34 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 09, 2026, 09:42 AM UTC
This incident has been resolved.
Hub not accessible
Affected: Hub
Timeline · 4 updates
- investigating Nov 22, 2025, 02:44 AM UTC
We are experiencing an issue where users are unable to login into their Hub. We are working to address the underlying cause and minimizing impact.
- identified Nov 22, 2025, 02:55 AM UTC
We have identified the issue and are currently implementing a fix.
- monitoring Nov 22, 2025, 04:04 AM UTC
A fix has been implemented and we are monitoring. User should now be able to login into their hub.
- resolved Nov 22, 2025, 11:17 PM UTC
This issue is resolved.
Facebook mentions not discoverable
Affected: Hub
Timeline · 7 updates
- identified Nov 22, 2025, 08:58 AM UTC
Meta, our Facebook mention provider in Respond is currently experiencing issues with their APIs which means that we are unable to match facebook mentions to dives. We have contacted Meta and are currently working on a solution to restore service for all Respond clients that currently have an integrated facebook account.
- identified Nov 22, 2025, 11:21 PM UTC
The team has updated Respond clients saved dives to be able to more precisely target facebook mentions. We are still working with Meta for a resolution on this issue.
- identified Nov 22, 2025, 11:22 PM UTC
The team has updated Respond clients saved dives to be able to more precisely target facebook mentions. We are still working with Meta for a resolution on this issue.
- identified Nov 24, 2025, 02:19 AM UTC
We are still working with Meta for a resolution on this issue. We will update this thread once we receive an update.
- identified Nov 25, 2025, 02:35 AM UTC
We are continuing to work with Meta for a fix on this issue.
- monitoring Dec 01, 2025, 01:11 AM UTC
Meta acknowledged the issue and pushed a fix this morning. The team is currently monitoring.
- resolved Dec 02, 2025, 12:03 AM UTC
This incident has been resolved.
Meta API Issues Affecting Facebook Connections
Affected: ConversationsIntegrations
Timeline · 2 updates
- investigating Oct 29, 2025, 03:24 AM UTC
Lexer has detected an elevated number of errors from Meta’s API impacting Facebook Pages and Business Accounts. This issue is currently affecting Lexer’s Respond and Activate products. As a result, you may experience: • Account disconnections (including email alerts) • Errors when syncing audiences • Errors when publishing replies to messages This issue originates within Meta’s systems and cannot be resolved by Lexer. We are actively monitoring the situation and will provide updates as more information becomes available from Meta.
- resolved Oct 29, 2025, 05:10 AM UTC
Meta’s API errors impacting Facebook Pages and Business Accounts have now been resolved. Affected accounts have reconnected successfully, and normal functionality has resumed across Lexer’s Respond and Activate products. We’ll continue to monitor performance, but no further impact is expected.
Hub.lexer.io - service disruption
Affected: Hub
Timeline · 5 updates
- investigating Aug 20, 2025, 12:09 AM UTC
We’re investigating an issue causing degraded performance on hub.lexer.io. The service has automatically recovered, and we’re continuing to monitor stability.
- investigating Aug 20, 2025, 12:09 AM UTC
We are continuing to investigate this issue.
- monitoring Aug 20, 2025, 12:19 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 20, 2025, 02:50 AM UTC
We are continuing to monitor for any further issues.
- resolved Aug 20, 2025, 06:16 AM UTC
This incident has been resolved.
File Upload API and Secure File Upload Outage
Timeline · 1 update
- resolved Jun 03, 2025, 01:30 AM UTC
Partial service outage affecting file uploads 28 May 2025 08:00 AEST – 3 June 2025 11:00 AEST Between 08:00 AEST on 28 May 2025 and 11:00 AEST on 3 June 2025, Lexer experienced an outage affecting two upload methods: the File Upload API and the Secure File Upload (drag and drop) feature. During this period, all file upload attempts via these channels failed. If you attempted to upload files between 28 May and 3 June via the affected methods, please reupload them to ensure they are processed. The issue was resolved as of 11:00 AEST on 3 June 2025. File uploads are now functioning as expected. We apologise for the disruption and appreciate your understanding.
Hub.lexer.io performance degraded
Affected: Hub
Timeline · 6 updates
- investigating Feb 17, 2025, 11:43 PM UTC
We're investigating reports of degraded performance for hub.lexer.io.
- investigating Feb 17, 2025, 11:43 PM UTC
We are continuing to investigate this issue.
- identified Feb 17, 2025, 11:55 PM UTC
We are experiencing a high rate of search timeout errors when loading conversations in Listen and Respond. Our team is continuing to investigate the root cause.
- identified Feb 18, 2025, 02:28 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 18, 2025, 04:57 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 19, 2025, 05:24 AM UTC
This incident has been resolved.