Live / Bit2Me / Incident
Bit2Me: Cambio programado en Social Pay — efectivo el 8 de octubre de 2026 // Scheduled change — Social Pay — effective 8 October 2026
Bit2Me · bit2me.comidentified2026-09-29 08:31 UTC
Public — what happened
Summary
Bit2Me posted a notice on 29 September 2026 about a planned change to its Social Pay service taking effect on 8 October 2026, rather than reporting an outage. The company said that from that date, money moved between a subaccount and its main user through Social Pay transfers will no longer be settled automatically; instead, each transfer will create an order and the funds will stay on hold until a separate claim step is completed. Bit2Me said this affects businesses whose software connects to its API to move funds this way, and asked them to add the claim step before the deadline, warning that transfers without it will not deliver funds after that date.
Timeline
- Started — 2026-09-29 08:31 UTC
- Identified — 2026-09-29 08:31 UTC
- Ongoing at last check.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Bit2Me against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Bit2Me: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Bit2Me report →
More from Bit2Me
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.