Live / Bit2Me / Incident
Bit2Me: API Update: Endpoint Deprecation
Bit2Me · bit2me.commonitoring2026-07-09 14:20 UTC
Public — what happened
Summary
Bit2Me posted a notice on July 9, 2026 at 14:20 UTC saying it plans to retire a long list of older API endpoints on January 11, 2027, covering areas such as account details, password resets, cards, trading settings, tax reports, wallet transactions and stock-related functions. The company said only people whose integrations still rely on those older endpoints will be affected, and it has published newer replacement versions on its official API site. Bit2Me asked developers to switch to the updated endpoints before the cutoff date and to reach out to support if they need help. The notice is marked as monitoring and does not describe an outage.
Timeline
- Started — 2026-07-09 14:20 UTC
- Monitoring — 2026-07-09 14:20 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