abizon

Faultlines

Everything we've broken

When a visa is late, someone misses a flight. That is not the kind of failure you get to quietly resolve in a private channel. Every incident that reached a traveller is written up here, in full, permanently.

Why this page exists

An incident log you only publish when the news is good is marketing. This one includes the outage that cost us the most money and the near-miss on document access that we would have preferred nobody ever knew about. If it affected a traveller, it is here.

No incidents published

abizon has not filed applications at volume yet, so there is no operational history to write up. When there is, every incident that affected a traveller appears here with its cause and what changed — including the ones that are embarrassing to publish.

    Policy

    What gets published here

    An incident is written up on Faultlines if it meets any of these tests. We do not get to decide case by case after the fact.

    • A traveller received their visa later than the date we committed to
    • A traveller was charged incorrectly, in either direction
    • Personal data was, or could have been, exposed to anyone not entitled to it
    • An application was submitted with information the traveller did not supply
    • Our published statistics were wrong and had to be restated

    Timeline

    A holding entry goes up within 72 hours of resolution. The full post-mortem follows within ten working days. We do not wait for the fix to ship before publishing the cause.

    What we leave out

    Names of individual employees, and any detail that would identify an affected traveller. Everything else — including the parts that make us look careless — stays in.

    See the operating numbers

    Approval rates, on-time delivery and refunds paid, published quarterly with the misses included.

    Transparency report