Previous version. This is the text that applied until 3 October 2026. It stays in force for customers who signed up before 4 October 2026 until 3 November 2026. Read the current version. All previous versions.
Effective Date: February 2026 | Service: Limitguard Trust Intelligence API | Provider: Ambulatio Consulting BV, The Netherlands
Service tiers
Free / Developer
No formal uptime commitment. Suitable for development and testing.
- Sandbox mode available
- Community support (docs)
- No SLA credits
- Shared rate limits
Growth
Up to 43.8 minutes downtime per month. Suitable for production workloads.
- Monthly uptime: 99.9%
- P95 latency: <500ms
- Email support, 24h response
- 10% credit per 0.1% below SLA
Enterprise
Up to 21.9 minutes downtime per month. For mission-critical integrations.
- Monthly uptime: 99.95%
- P95 latency: <300ms
- Priority support, 4h response
- 25% credit per 0.1% below SLA
1. Definitions
| Term | Definition |
|---|---|
| Uptime | Percentage of minutes in a calendar month during which the API returns valid responses to health check requests |
| Downtime | Consecutive 5-minute period where the API health check endpoint returns no response or HTTP 5xx for >50% of requests |
| Scheduled Maintenance | Planned downtime announced at least 72 hours in advance via status.limitguard.ai |
| Monthly Uptime Percentage | (Total minutes in month - Downtime minutes) / Total minutes in month × 100 |
2. Measurement method
Uptime is measured by BetterStack, an independent third-party monitoring service. Monitoring checks the /health endpoint every 60 seconds from multiple geographic locations. The public status page is available at status.limitguard.ai.
Historical uptime data is published on the status page and retained for 90 days. Customers may request uptime reports for any period within the retention window by emailing support@limitguard.ai.
When an incident has occurred, a post-mortem is published in the documentation. The most recent covers the outage of 2026-06-19 to 2026-09-05: read the post-mortem.
3. Scheduled maintenance
We reserve up to 4 hours per calendar month for scheduled maintenance. Scheduled maintenance windows are:
- Announced at least 72 hours in advance on the status page
- Notified via email to registered users on paid plans
- Scheduled outside peak usage hours where possible (02:00 to 06:00 CET)
- Excluded from downtime calculations for SLA credit purposes
4. Exclusions
The following are not counted as downtime for SLA purposes:
- Scheduled maintenance windows (up to 4 hours per month, 72 hours notice given)
- Downtime caused by customer-side network issues, misconfigured API calls, or invalid credentials
- Events beyond our reasonable control: natural disasters, widespread internet outages, upstream provider failures affecting all cloud regions simultaneously
- Degraded performance resulting from customer exceeding documented rate limits
- Third-party data source unavailability (KVK registry, OpenSanctions) affecting specific checks only. The core API remains available
- Free / Developer tier accounts (best effort, no SLA commitment)
5. Credit calculation
| Growth: Actual Monthly Uptime | Service Credit |
|---|---|
| 99.9% and above | None |
| 99.0% to 99.89% | 10% of monthly fees |
| 95.0% to 98.99% | 25% of monthly fees |
| Below 95.0% | 50% of monthly fees |
| Enterprise: Actual Monthly Uptime | Service Credit |
|---|---|
| 99.95% and above | None |
| 99.0% to 99.94% | 25% of monthly fees |
| 95.0% to 98.99% | 50% of monthly fees |
| Below 95.0% | 100% of monthly fees |
Credits are applied to the next monthly invoice. Credits do not accumulate across months. Total credits in any calendar month shall not exceed the monthly fees paid for that month.
6. Claim process
- Submit a credit claim within 30 days of the incident by emailing support@limitguard.ai
- Include the subject line "SLA Credit Claim" and specify the affected time period
- We will review the claim against BetterStack monitoring data within 10 business days
- Approved credits will appear on the next monthly invoice
- Claims submitted after the 30-day window will not be processed
7. Sole remedy
Service credits described in this SLA are the customer's sole and exclusive remedy for any failure by Ambulatio Consulting BV to meet the uptime commitments in this agreement. Credits are not refunds and do not affect any other terms of the service agreement. This SLA does not limit Ambulatio Consulting BV's liability under applicable law for damages caused by gross negligence or wilful misconduct.
Questions about this SLA? Contact support@limitguard.ai or consult the real-time status page.
