1. Service Availability
MIR targets 99.9% monthly uptime for the API and platform services, measured as:
What counts as downtime
- API endpoints returning 5xx errors for more than 5 consecutive minutes
- Complete inability to submit events or query participation history
What does not count as downtime
- Scheduled maintenance with 72 hours advance notice
- Issues caused by the partner's systems, network, or misuse
- Force majeure events (natural disasters, government actions, widespread internet outages)
- DigitalOcean platform-level outages beyond MIR's control
2. Scheduled Maintenance
- Maintenance windows will be communicated at least 72 hours in advance
- Maintenance will be scheduled during low-traffic hours when possible
- Rolling deploys are used to minimize disruption -- most deployments require zero downtime
3. API Response Time
MIR targets the following response times under normal operating conditions:
| Endpoint | Target p95 |
|---|---|
POST /v1/events |
< 500ms |
POST /v1/events/bulk |
< 2000ms |
GET /v1/resolve |
< 300ms |
POST /v1/policy/evaluate |
< 500ms |
These are targets, not guarantees. Actual performance may vary based on payload size, network conditions, and system load.
4. Support
| Channel | Response Target |
|---|---|
| Email (security@myinternetreputation.org) | Within 24 hours (business days) |
| Critical security incidents | Within 4 hours |
Founding enterprise partners receive direct access to the founder for technical and integration support.
5. Data Durability
- PostgreSQL database with automated daily backups
- Database standby node for automated failover
- Backup retention: managed by DigitalOcean (7-day default)
6. Service Credits (Founding Partners)
If monthly uptime falls below the target:
| Uptime | Credit |
|---|---|
| 99.0% - 99.9% | 5% of monthly fee |
| 95.0% - 99.0% | 10% of monthly fee |
| Below 95.0% | 25% of monthly fee |
Credits are calculated automatically on the 1st of each month based on the previous month's uptime. Credits are applied to your next billing cycle and do not exceed one month's fee. No request required.
7. Termination
Either party may terminate with 30 days written notice. Upon termination:
- Partner API keys are revoked
- Partner-submitted event data is retained for 90 days, then deleted
- No refunds for partial months
8. Changes to This SLA
MIR may update this SLA with 30 days notice. Existing contracts honor the SLA in effect at signing for the duration of the contract term.
Contact: security@mirregistry.org