inFlow - Some disruptions to Messaging post migration from On-premise to Cloud API for some numbers – Incident details

Some disruptions to Messaging post migration from On-premise to Cloud API for some numbers

Resolved
Operational
Started about 1 year agoLasted 1 day

Affected

inFlow Portal

Degraded performance from 4:44 AM to 1:37 PM, Partial outage from 1:37 PM to 1:29 PM

inFlow Broadcast

Degraded performance from 4:44 AM to 1:37 PM, Partial outage from 1:37 PM to 1:29 PM

inFlow Partner APIs

Degraded performance from 4:44 AM to 1:37 PM, Partial outage from 1:37 PM to 1:29 PM

Updates
  • Resolved
    Resolved
    • Resolved

      February 18, 2025 at 6:41 PM

      The issue is impacting a small number of migration attempts from the On-Premise API to the Cloud API, with Meta returning an error during the migration process.

      As this affects only a limited number of requests, we are removing the incident from our status page. However, if your migration fails, please submit a support request, and our team will assist you on a case-by-case basis.

  • Update
    Update
    • Update

      February 18, 2025 at 2:25 PM

      We´re still working with the Meta engineering team on this issue. We´ll provide a new update once we have any news.

  • Update
    Update
    • Update

      February 17, 2025 at 5:26 PM

      We are continuing to work with Meta Engineering team on this problem. We'll update again as soon as possible.

  • Investigating
    Investigating
    • Update

      February 17, 2025 at 7:14 AM

      We are aware of an issue that is impacting Messaging for some numbers after migration from On-premise to Cloud API. Our engineering team is currently investigating it with Meta Engineering team. We'll update again as soon as possible.

    • Investigating

      February 15, 2025 at 10:44 PM

      We are aware of an issue that is impacting Messaging for some numbers after migration from On-premise to Cloud API. Our engineering team is currently investigating it with Meta Engineering team. We'll update again as soon as possible.