pingoru pingoru Notabene had 26 outages in the last 2 years totaling 265h 6m of downtime, averaging 1.1 incidents per month.
There were 26 Notabene outages since February 17, 2025 totaling 265h 6m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We're currently investigating the degraded performance of our customer-facing API.
We've now resolved the incident. Thanks for your patience.
We identified an issue affecting the processing of Travel Rule transfers from Notabene V2 to V1, causing some transfers to remain pending instead of being automatically processed. The underlying issue has been resolved, and our team is working to replay all affected messages to ensure they are processed successfully. **No action is required from customers.** We will continue monitoring the situation and provide an update once all affected transfers have been processed. We apologize for the disruption.
We've now resolved the incident. Thanks for your patience.
This incident has been resolved.
During planned infrastructure maintenance in our EU region, our internal message system was briefly unable to accept writes. Between 08:15 and 10:10 UTC, some transactions submitted through the API were delayed. A smaller number were accepted but never processed, so they stayed in a pending state. The API stayed available throughout. Most of the impact fell between 08:54 and 09:10 UTC and between 09:37 and 09:50 UTC.
Impact: From 14 Sep 18:14 UTC to 15 Sep 08:41 UTC, calls to POST /entities/{did}/address-ownership/discover on api.eu1.notabene.id timed out without a response. All other API endpoints, including transfer creation and authorization, were unaffected. Sandbox was unaffected. Customers using discovery as a step in their withdrawal flow saw those withdrawals held for the duration. Timeline - 14 Sep 18:14 — A network security rule permitting our EU production cluster to reach the internal address hash service was removed during infrastructure work. Discovery requests began timing out. - 15 Sep 08:21 — Customer reports received. Incident opened. - 15 Sep 08:26 — Root cause identified as a missing network rule. - 15 Sep 08:41 — Rule restored. Discovery recovered immediately. No backlog processing was required, as failed requests had not been queued. - 15 Sep 10:15 — Permanent fix to the infrastructure module merged.
We are currently investigating an issue serving our API and UI.
This issue has been resolved and everything should be working normally now. We're continuing to monitor closely to make sure everything stays stable. Thank you so much for your patience while we worked through this.
While introducing more security layers to our systems, we blocked part of the communication between two services that ended up making the UI and API unavailable
We are currently investigating an availability issue in our Test API.
We've now resolved the incident. Thanks for your patience.
We've now resolved the incident. Thanks for your patience.
Resolved
We've now resolved the incident.
API has recovered. A short spike in 500 errors for approximately 1% of API calls between 05:35 and 05:45 UTC due to the downstream provider issues. We will continue to monitor.
We've now resolved the incident. Thanks for your patience.
We're continuing to monitor, but as of 14:32 UTC all systems are up and running.
We've now resolved the incident, and are continuing to monitor.
We've now resolved the incident. Thanks for your patience. The recovery started at 05:22:00 UTC
We've now resolved the incident. Thanks for your patience.
We've now resolved the incident. Thanks for your patience.
There was delay in sending webhook notifications. All messages were securely stored, with no data loss, and full functionality has been restored.
Due to over-aggressive DDoS mitigations, some customers may have been inadvertently blocked from accessing the Notabene API. These mitigations have been adjusted to better target attackers during the DDoS attack.
We've resolved an issue which was related to a stricter security group setup during yesterday's DDoS attempts. We apologize for the inconvenience.
We've now resolved the incident. Thanks for your patience.
We've now resolved the incident. Thanks for your patience.
We've now resolved the incident. Thanks for your patience.