How we know: the official Bit2Me status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works
Bit2Me Component Status
1 of 34 Bit2Me components are impaired. Worst problems listed first.
1degraded33operational
Payment Methods (Cash - In / Cash - out) » PIX Brazil
Degraded
Mobile APP » Android
Operational
Mobile APP » iOS
Operational
31 more components tracked
Their status is in the bar above. Free accounts see every component by name.
Also tracking Notifications » 2FA SMS, Notifications » E-Mails, Notifications » Push, Other » Academy, Other » Blog, Other » Careers, Other » News, Other » Web3MBA, Payment Methods (Cash - In / Cash - out) » Apple Pay, Payment Methods (Cash - In / Cash - out) » Credit / Debit Card, Payment Methods (Cash - In / Cash - out) » CVU Argentina, Payment Methods (Cash - In / Cash - out) » Google Pay, and 19 more.
Component statuses may change independently during partial outages.
Recent Bit2Me Outages & Incidents
Incident history from the official Bit2Me status page, including resolution updates.
Retrasos en la entrega de SMS / SMS delivery delaysResolved Sep 23, 2026 · 6h 24mResolved
This incident has been resolved.
---
[2026-09-23T21:57:38.395+02:00] (monitoring) We are continuing to monitor for any further issues.
---
[2026-09-23T15:33:36.158+02:00] (monitoring) Estamos detectando problemas en el envío de SMS. Algunos usuarios pueden no recibir, o recibir con retraso, los códigos de verificación enviados por SMS (inicio de sesión, verificación en dos pasos o autorización de dispositivos).
Nuestro equipo técnico ya está trabajando junto a nuestro proveedor para resolverlo lo antes posible.
Mientras tanto, te recomendamos esperar unos minutos antes de solicitar un nuevo código, ya que varias solicitudes seguidas pueden bloquear temporalmente el envío.
Tus fondos y tu cuenta están seguros. Actualizaremos esta página en cuanto tengamos más información.
Sentimos las molestias.
----------
We are detecting issues with SMS delivery. Some users may not receive verification codes sent by SMS, or may receive them with a delay (sign-in, two-step verification, or device authorization).
Our technical team is already working with our provider to resolve this as soon as possible.
In the meantime, we recommend waiting a few minutes before requesting a new code, as several requests in a row can temporarily block delivery.
Your funds and your account are safe. We will update this page as soon as we have more information.
We apologize for the inconvenience.
Migración de Icon (ICX) a SodaX (SODA) / Icon (ICX) to SodaX (SODA) MigrationStarted Sep 21, 2026Investigating
Icon (ICX) ha migrado a un nuevo criptoactivo, SodaX (SODA). En Bit2Me hemos dado soporte a esta migración y ya está completada: tus ICX son ahora SODA con un ratio 1:1, sin que hayas tenido que hacer nada.
Para ejecutar la migración con garantías, desde el 14 de agosto de 2026 estuvieron pausadas la compra, la venta, el swap y las transferencias de entrada y salida (depósitos y retiros) de este criptoactivo.
Desde el 21 de septiembre de 2026, la operativa con SODA ha quedado restablecida con normalidad:
- Compra: Disponible
- Venta: Disponible
- Swap: Disponible
- Depósito: Disponible
- Retirada: Disponible
La migración se ha aplicado de forma automática sobre tu saldo. No es necesario reclamar el cambio, ejecutar ninguna operación ni actualizar nada en la app.
Para cualquier duda, contacta con nuestro equipo de soporte.
----------
Icon (ICX) has migrated to a new crypto-asset, SodaX (SODA). At Bit2Me we have supported this migration and it is now complete: your ICX is now SODA at a 1:1 ratio, with no action needed on your side.
To carry out the migration safely, buying, selling, swapping and incoming and outgoing transfers (deposits and withdrawals) of this crypto-asset were paused from August 14th, 2026.
As of September 21st, 2026, operations with SODA have been restored to normal:
- Purchase: Available
- Sale: Available
- Swap: Available
- Deposit: Available
- Withdrawal: Available
The migration has been applied to your balance automatically. You do not need to claim the change, carry out any transaction, or update anything in the app.
For any questions, contact our support team.
This incident has been resolved.
---
[2026-09-01T12:13:29.831+02:00] (monitoring) Bit2Me deslistará Bifrost Native Coin (BNC) a partir del 11 de septiembre de 2026, después de que este criptoactivo haya dejado de cumplir nuestros criterios de listado conforme a la revisión periódica de activos y al marco regulatorio aplicable.
El estado de las funcionalidades antes y después de esa fecha es el siguiente:
- Compra: No disponible (antes y después del 11/09/2026)
- Venta: Disponible hasta el 11/09/2026 a las 16:00 CEST (según condiciones de mercado) / No disponible a partir de esa fecha
- Retirada a wallet externa: Disponible (si existe red compatible) antes y después del 11/09/2026
- Depósito: No disponible (antes y después del 11/09/2026)
- Custodia / visualización de saldo: Disponible (antes y después del 11/09/2026)
Podrás vender BNC hasta el 11 de septiembre de 2026 a las 16:00 CEST, siempre que las condiciones de mercado lo permitan. A partir de ese momento, la única operación posible será retirarlo a una wallet externa, siempre que exista una red compatible.
A partir del 11 de septiembre de 2026 a las 16:00 CEST no podrás comprar, vender ni depositar BNC. Si tienes posiciones, órdenes u operaciones abiertas asociadas a BNC en otros servicios de Bit2Me, podrán cancelarse o liquidarse según los Términos y Condiciones de cada servicio. Te recomendamos revisarlas antes de esa fecha.
Bit2Me no garantiza la liquidez, recompra, precio de reembolso, valor de mercado, conversión ni compensación por pérdidas asociadas a este criptoactivo. Su valor puede fluctuar significativamente y, en situaciones de iliquidez o falta de soporte técnico, puede resultar imposible venderlo, retirarlo o recuperar su valor económico.
Para cualquier duda, contacta con nuestro equipo de soporte
----------
Bit2Me will delist Bifrost Native Coin (BNC) as of September 11th, 2026, following a periodic review of listed assets in accordance with our listing criteria and the applicable regulatory framework.
The status of the functionalities before and after that date is as follows:
- Purchase: Not available (before and after 11/09/2026)
- Sale: Available until 11/09/2026 at 16:00 CEST (subject to market conditions) / Not available after that date
- Withdrawal to external wallet: Available (if a compatible network exists) before and after 11/09/2026
- Deposit: Not available (before and after 11/09/2026)
- Custody / balance display: Available (before and after 11/09/2026)
You will be able to sell BNC until September 11th, 2026 at 16:00 CEST, subject to market conditions. After that time, the only available operation will be withdrawal to an external wallet, provided a compatible network exists.
From September 11th, 2026 at 16:00 CEST, purchasing, selling and depositing BNC will no longer be possible. If you have open positions, orders or operations associated with BNC in other Bit2Me services, these may be cancelled or settled in accordance with the Terms and Conditions of each service. We recommend reviewing them before that date.
Bit2Me does not guarantee the liquidity, repurchase, redemption price, market value, conversion or compensation for losses associated with this crypto asset. Its value may fluctuate significantly and, in situations of illiquidity or lack of technical support, it may be impossible to sell, withdraw or recover its economic value.
For any questions, contact our support team.
Bit2Me Uptime History
Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Bit2Me incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.
Uptime history50 days observed
Aug 8100.00% average · 50 days with incidentsSep 26
Live Bit2Me Outage Reports
Problems reported by engineers using Bit2Me. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.
Reports, last 24 hours0 total
24h agoNothing reportednow
No Bit2Me problems reported yet.
Are you seeing Bit2Me problems too?
Reports are anonymous, take about ten seconds, and help the next engineer who checks.
About Bit2Me
Bit2Me publishes a public status page at status.bit2me.com covering 40 components, including Services, Public Website and Android. PulsAPI tracks Bit2Me outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.
Over the past 30 days, PulsAPI has measured Bit2Me uptime at 100.00%. Response times, incident history, and SLA tracking for Bit2Me are available on the PulsAPI dashboard.
Bit2Me Status FAQ
Is Bit2Me down right now?
The verdict at the top of this page comes from the latest poll of the official Bit2Me status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.
What should I do if Bit2Me is not working?
Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Bit2Me recovers.
How do I check Bit2Me uptime history?
PulsAPI tracks Bit2Me uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Bit2Me changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.
How fast does PulsAPI detect Bit2Me outages?
PulsAPI reads the official Bit2Me status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.
Does PulsAPI track individual Bit2Me components?
Yes. PulsAPI monitors 34 individual Bit2Me components, so you can see which service or region is affected instead of a generic "service degraded" banner.
Can I get alerts when Bit2Me goes down?
Yes. Create a free account and subscribe to Bit2Me: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.
How do I report an issue with Bit2Me to the community?
Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Bit2Me problems early. Official status pages often lag real incidents by 10 to 20 minutes.
Is there a free way to monitor Bit2Me?
Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Bit2Me plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.
Track Bit2Me with the rest of your stack
2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.
