Live  /  Bit2Me  /  Incident

Bit2Me: Cambio programado: precisión decimal en Bit2Me Pro Trading Spot API / Scheduled Change: Decimal Precision in Bit2Me Pro Trading Spot API

Bit2Me · bit2me.commonitoring2026-08-12 10:29 UTC
Public — what happened

Summary

Bit2Me posted an advance notice on 12 August 2026 about a planned change to its Pro Trading Spot API, rather than reporting an outage. The company said that starting 10 February 2027, certain numeric fields for trades, orders and balances, such as price, amount, fees and blocked balance, will carry up to 18 decimal places. Bit2Me asked developers who connect to the API to check that their systems can read, round, store and reconcile numbers with that many decimals, and to contact their usual Bit2Me support contact with questions. The notice remains open with a monitoring status.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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

The full archive is on the Bit2Me status & history page.

Related: Bit2Me status & history. SquidGrid is not affiliated with Bit2Me.