Live / Bit2Me / Incident
Bit2Me: Cambios en la API en la gestión de las URLs que terminan con / final // Change to how the API handles URLs that end with a slash
Bit2Me · bit2me.commonitoring2026-10-07 10:08 UTC
Public — what happened
Summary
Bit2Me said it is changing how its API treats web addresses that have a slash at the end, a planned change rather than a reported outage. Starting 7 October 2026, the company said such requests are automatically forwarded to the same address without the slash, and software that follows these redirects should keep working normally. Bit2Me said that from 7 April 2027 it will stop forwarding them, and those requests will instead fail with a not-found error. Addresses without a trailing slash are not affected, according to the company, and the notice remains under monitoring.
Timeline
- Started — 2026-10-07 10:08 UTC
- Monitoring — 2026-10-07 10:08 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 42, 2026, our weekly internet health report.