Lexer incident

Facebook mentions not discoverable

Major Resolved View vendor source →

Lexer experienced a major incident on November 21, 2025 affecting Hub, lasting 10d 11h. The incident has been resolved; the full update timeline is below.

Started
Nov 21, 2025, 12:45 PM UTC
Resolved
Dec 02, 2025, 12:03 AM UTC
Duration
10d 11h
Detected by Pingoru
Nov 21, 2025, 12:45 PM UTC

Affected components

Hub

Update timeline

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. identified Nov 25, 2025, 02:35 AM UTC

    We are continuing to work with Meta for a fix on this issue.

  6. monitoring Dec 01, 2025, 01:11 AM UTC

    Meta acknowledged the issue and pushed a fix this morning. The team is currently monitoring.

  7. resolved Dec 02, 2025, 12:03 AM UTC

    This incident has been resolved.