Checking status…

Service Status

Real-time monitoring of the Parse invoice extraction API

Last checked: —

View uptime →
History on UptimeRobot
—
Average /extract latency
—
Active API version
Service components
🔌
API — /v1/extract
OCR + AI invoice extraction
— ms Checking
🖊️
API — /v1/convert 🇪🇸 ES
Facturae generation and XAdES-BES signing — not used by the Parse extraction API itself
— ms Checking
🗄️
Database
SQLite — invoice and user storage
Checking
☁️
B2 Storage 🇪🇸 ES
Legal custody of signed Facturae XMLs (4 years) — Parse itself doesn't store uploaded invoice files
Checking
💳
Payments — Stripe
Subscriptions and credit packs
Checking
Availability and incident history
📊 Full availability and incident history, updated in real time. View on UptimeRobot →
Service policy
SLA and commitments
Target uptime
99.5% monthly
≤ 3.6h of downtime per month
P95 response time
< 8s for /extract
< 3s for /convert (JSON→XML)
API versioning
Versions maintained for at least 12 months after a deprecation notice.
Active version: v1
Incident notification
Email to active customers within < 30 min.
This page updates every 60s.
Scheduled maintenance
Sundays 03:00–05:00 CET.
Minimum 48h notice by email.
Data custody
Uploaded invoice files are processed in memory and discarded immediately — only the extracted JSON is stored.
🇪🇸 Spain-only: signed Facturae XMLs are kept in Backblaze B2 for a minimum of 4 years ("Ley Crea y Crece").
Performance benchmark
Load test — POST /sign (XAdES-BES signing) 🇪🇸 ES Last run: May 24, 2026
This benchmark is for the Spain-only Facturae signing pipeline, not the Parse extraction API. For live /extract latency, see the "Average /extract latency" card at the top of this page.
Conditions: 100 requests · 10 concurrent workers · real FNMT certificate · full XAdES-BES signature validated by VALIDe · Hetzner CX22 server (2 vCPU, 4GB RAM)
Success rate
100% 100/100 requests
Throughput
3.5 req/s sustained
Minimum latency
436 ms
Average latency
2.7 s
95th percentile
8.6 s under artificial load
Peak CPU / load avg
96% peak load avg 0.41 / 2.00
RAM used
572 MB of 3.73 GB available (15%)
Errors
0 no timeouts or server errors
Note on p95: The 8.6s 95th percentile occurs under an artificial load of 10 simultaneous workers — equivalent to 10 invoices being signed at exactly the same millisecond. Under real production traffic, typical latency is 400ms–1.5s per signature. The bottleneck under high concurrency is SQLite (sequential writes), not CPU or the cryptographic signing itself.